How to create an S3 bucket to receive Unacast data

The first step of the delivery process is to configure an S3 bucket for Unacast to deliver the data to. You'll need to have access to your organization's Amazon Web Services (AWS) console with privileges to create an S3 bucket. To begin, please follow the instructions below, which should only take a few minutes to complete.

1. Sign in to the AWS S3 console.
2. Create an S3 bucket that you want to receive Unacast data in (e.g. s3://my-company-uc-data).
3. Create a policy for Unacast to access the bucket and prefix by first selecting the Permissions
4. Click on the Edit button under Bucket Policy.
5. Copy this bucket policy as formatted below and paste it into the permission editor:

{
   "Statement": [
       {
           "Action": [
               "s3:PutObject",
               "s3:PutObjectTagging",
               "s3:PutObjectVersionTagging",
               "s3:GetObject",
               "s3:DeleteObject",
           ],
           "Effect": "Allow",
           "Principal": {
               "AWS": [
                   "arn:aws:iam::024015676143:user/unacast-file-delivery"
               ]
           },
           "Resource": "arn:aws:s3:::{{bucketName}}/{{data prefix}}/*",
           "Sid": "UnacastWrite"
       },
       {
           "Action": "s3:ListBucket",
           "Effect": "Allow",
           "Principal": {
               "AWS": [
                   "arn:aws:iam::024015676143:user/unacast-file-delivery"
               ]
           },
           "Resource": "arn:aws:s3:::{{bucketName}}",
           "Condition": {
                "StringLike": {
                    "s3:prefix": "{{data prefix}}/*"
                }
            },
           "Sid": "UnacastVerify"
       }
   ],
   "Version": "2012-10-17"
}

Include your bucket name in the policy

When pasting the policy above, please make sure to substitute your bucket name and path for {{bucketName}} when specifying the resource. Also substitute the prefix for {{data prefix}} in the bucket you want the data to go into - note that this is case sensitive. Be sure to provide us with this prefix.

1. Click Save changes.
2. Please send your customer success manager the following information:

• The name of your bucket
• The prefix you chose
• The region the bucket is in, for instance us-east-1

3. Under Object Ownership, ensure object ownership is changed from the default value. This setting should be set on the bucket as
   Bucket owner preferred
   or
   Bucket owner enforced

Do not set up KMS encryption Please do not enable KMS encryption when configuring the bucket. We will not be able to write to your S3 bucket if you enable this setting.