Configuring and exporting to a S3 cross account destination
|This functionality isn't available as standard to all users. Please contact your InfoSum representative to learn more about how to gain access.|
You can use an S3 cross account destination to:
- Export query results to an Amazon S3 bucket with cross account authentication.
Once a destination is created, you need only provide run time variables to push an activation file to a remote resource. Saved destinations are available to all users in your company and can be reused indefinitely. Destinations are similar to push connectors, but destinations do not require you to re-enter location information each time data is exported. Destinations are currently only compatible with owned activation datasets.
Creating an S3 access key destination
First, select the Destinations tab under Collaborate and then click New Destination.
The form below appears when you select S3 Cross Account as your destination type. The following fields need to be completed:
- Destination Type: Select S3 cross account.
- Name: Identifies the destination
- Description: A free-text explanation of the destination
Once completed, press Next.
Adding S3 cross account connection details
Use destinations to create a connection between the InfoSum Platform and your Amazon S3 bucket with cross account authentication
The above form contains the following fields:
S3 connection details
- Bucket: Specify the bucket name (no leading s3 identifier, e.g. "bucket-name" not "s3://bucket-name")
- Region: Specify the AWS region of your bucket
- Path: Specify the path within the bucket.
- Principal: InfoSum generated ARN. You need to enable the ARN in this field to recognise the User Role that is supplied in number 3 below. To do this, go to your AWS account and replace the text in the Trust Policy with the InfoSum trust relationship policy as described in configuring AWS IAM for the InfoSum S3 cross-account data connector.
- External ID: InfoSum generated ID per user email domain. You should use this external ID, along with the Principal for an extra validation when allowing the assumption of their push role
- Push Role ARN: You need to create a role that has a Permissions Policy that allows writing to their S3 bucket. The expected format of the ARN entered here is:
- Session name: User defined session
Click Submit. The saved destination is stored in the Platform’s Destinations page and can be selected in the Activations tab when pushing an activation file to a remote resource. The destination can be reused and is available to all users in your company.
Exporting results to a destination
After creating an activation, you can export activation query results to a preconfigured destination. This allows you to export data to a location without re-entering your destination configuration and security credentials.
You can activate results to a file using either Segment Builder or the Query Tool. Go to the Activation tab under Activate, where you will see some information about the campaign and its status. The total rows give you an insight into the size of the file before pushing it to the destination.
At the bottom of the page, you will see a box providing more details on the campaign, such as the query used and the name of the output column. There are three menu tabs within this box - Details, Export Configuration and Export History.
Once you've exported the results, the details and status will be viewable under the Export History tab.
Switch to Export Configuration and select Destination. Contact your Customer Support Representative contact if the Destination option does not appear.
Select a destination from the list or click Create New to create a new destination. For tutorials on how to create destinations, please see How to create a destination.
Depending on the selected destination type, you may need to enter run-time details in the export configuration fields, as described in the tables below.
S3 cross account export configuration fields
You can define the filename and file extension ( e.g. pushfile.csv) when exporting a file to an S3 destination.
Optionally, you can override the path specified in the S3 Destination.
When you have completed the required fields, click Export to Destination. Selecting this button begins the file stream.