Creating a Data Delivery
Scenario
SecMaster can deliver data to other pipelines or other cloud products in real time so that you can store data or consume data with other systems. After data delivery is configured, SecMaster periodically delivers the collected data to the specified pipelines or cloud products.
Currently, data can be delivered to the following cloud products: Object Storage Service (OBS) and Log Tank Service (LTS).
This section describes how to create a data delivery task.
Prerequisites
- If you want to deliver data to an OBS bucket, the bucket must have private, public read, or public read/write policy enabled. Currently, parallel file buckets are not supported. For details, see Creating an OBS Bucket.
- To deliver data to LTS, ensure there is an available log group and log streams. For details, see Managing Log Groups and Managing Log Streams.
Limitations and Constraints
When performing cross-account delivery, the data can only be delivered to the pipelines instead of cloud services of other accounts.
Creating a Data Delivery
- Log in to the management console.
- Click in the upper left corner of the management console and select a region or project.
- Click in the upper left corner of the page and choose Security & Compliance > SecMaster.
- In the navigation pane on the left, choose Workspaces > Management. In the workspace list, click the name of the target workspace.
Figure 1 Workspace management page
- In the navigation pane on the left, choose
. The security analysis page is displayed.Figure 2 Accessing the Security Analysis tab page
- In the data space navigation tree on the left, click the data space name to expand all pipelines. Next to the name of the target pipeline, click More > Deliver.
Figure 3 Accessing data delivery settings page
- (Optional) Confirm the authorization information, select Agree to authorize and click OK.
Authorization is required for the first delivery to a specific destination type. If the authorization has been performed, skip this step.
- On the Create Delivery page, set data delivery parameters.
- Configure basic information.
Table 1 Basic information Parameter
Description
Delivery Name
Customized delivery rule name
Resource Consumption
The value is generated by default and does not need to be configured.
- Configure the data source.
In the Data Source Settings area, the detailed information about the current pipeline is displayed. You do not need to set this parameter.
Table 2 Data source parameters Parameter
Description
Delivery Type
Delivery destination type. The default value is PIPE.
Region
Area where the current pipeline is located
Workspace
Workspace to which the current pipeline belongs
Data Spaces
Data space to which the current pipeline belongs
Pipeline
Pipeline name
Data Read Policy
Data read policy of the current pipeline
Read By
Identity of the data source reader
- Configure the delivery destination.
- PIPE: Deliver the current pipeline data to other pipelines of the current account or pipelines of other accounts. Set this parameter as required.
- Current: Deliver the current pipeline data to another pipeline of the current account. For details about the parameters, see Table 3.
Table 3 Destination parameters - Current account pipeline Parameter
Description
Account Type
Account type of the data delivery destination. Select Current.
Delivery Type
Delivery type. Select PIPE.
Workspace
Workspace where the destination PIPE is located
Data Spaces
Data space where the destination PIPE is located
Pipeline
Pipeline where the destination PIPE is located
Written To
The value is generated by default and does not need to be configured.
- Cross-account delivery: Deliver the current pipeline data to the pipeline of another account. For details about the parameters, see Table 4.
Table 4 Destination parameters - PIPE of Other account Parameter
Description
Account Type
Account type of the data delivery destination. Select Other.
Delivery Type
Delivery type. Select PIPE.
Account ID
ID of the account to which the destination pipeline belongs
Workspace ID
ID of the workspace where the destination PIPE is located. For details about how to query the workspace ID, see 7.
Data Space ID
ID of the data space where the destination PIPE is located. For details about how to query the data space ID, see 7.
Pipeline ID
ID of the pipeline where the destination PIPE is located. For details about how to query the pipeline ID, see 7.
Written To
The value is generated by default and does not need to be configured.
- Current: Deliver the current pipeline data to another pipeline of the current account. For details about the parameters, see Table 3.
- LTS: Deliver the pipeline data to LTS. For details about the parameter settings, see Table 5.
To deliver data to LTS, ensure there is an available log group and log streams. For details, see Managing Log Groups and Managing Log Streams.
Table 5 Destination parameters - LTS Parameter
Description
Account Type
Account type of the data delivery destination. When delivering data to LTS, only the Current account type can be selected.
Delivery Type
Delivery type. Select LTS.
Log Group
Destination LTS log group
Log Stream
Destination LTS log stream
Written To
The value is generated by default and does not need to be configured.
- OBS: Deliver the pipeline data to OBS. For details about the parameter settings, see Table 6.
Note that the OBS bucket you use must have private, public read, or public read/write policy enabled. Currently, parallel file buckets are not supported. For details, see Creating an OBS Bucket.
Table 6 Destination parameters - OBS Parameter
Description
Account Type
Account type of the data delivery destination. When delivering data to OBS, only the Current account type can be selected.
Delivery Type
Delivery type. Select OBS.
Bucket Name
Name of the destination OBS bucket
Written To
The value is generated by default and does not need to be configured.
- PIPE: Deliver the current pipeline data to other pipelines of the current account or pipelines of other accounts. Set this parameter as required.
- Under Access Authorization, view the permissions granted in 7.
A delivery request requires the read and write permissions to access your cloud resources. After the authorization, the delivery task can access your cloud resources.
- Configure basic information.
- Click OK.
Follow-up Operation
After a data delivery task is added, you need to grant the delivery permission. The delivery takes effect only after you accept the authorization. For details, see Data Delivery Authorization.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.