Setup

To enable Data Axle to upload files to your S3 bucket it is necessary to create an IAM policy for our IAM role. The role ID will be provided separately upon request. This policy is expected to look something similar to the below example, with the role and bucket details changed to real values.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AllowDataAxleBucketActions",
            "Effect": "Allow",
            "Principal": {
              "AWS": "role-provided-on-request"
            },
            "Action": [
                "s3:ListBucket",
                "s3:GetBucketLocation",
                "s3:PutObject",
                "s3:PutObjectAcl",
                "s3:GetObject",
                "s3:GetObjectAcl"
            ],
            "Resource": [
                "arn:aws:s3:::yourbucket"
                "arn:aws:s3:::yourbucket/*"
            ]
        }
    ]
}

File layout options

S3 deliveries support two file layouts. The default for S3 is Date-stamped.

• Flat — Objects are written under the configured S3 path with the delivery or subscription identifier and timestamp in the object name:

  • Subscriptions: subscription-{subscription_id}-{datestamp_timestamp}-{subscription_name}-{filename}
  • Standalone deliveries: delivery-{delivery_id}-{datestamp_timestamp}-{delivery_name}-{filename}

End the S3 path with / to deliver into that prefix. To add a filename prefix, put the text at the end of the path and do not end with /.

• Date-stamped — Objects are written under a date prefix: {s3_path}/{YYYYMMDD}/{filename}. Use this when you want deliveries grouped by date under the destination path. Filename prefix behavior (omitting the trailing /) applies only to flat layout; for date-stamped, the full path is treated as a directory prefix.

Example configurations: