Once configured for the relevant import or export, Dotdigital Personalization queries your S3 bucket for new data and fetches it when available.
Learn more about exporting data to AWS storage in Export data with the Firehose.
Before you start
This method does not support file-level encryption/GPG. We recommend enabling S3 bucket encryption in line with your company's security policy.
You can familiarize yourself with the data format to use for your files in the related articles:
Configure AWS storage
To setup your S3 storage for use with Personalization:
Create or select a bucket
Log in to your AWS account and either create a new bucket dedicated to Personalization or select an existing one.
Configure the bucket’s permissions
Once your bucket is ready, follow these steps to grant Personalization access:
Go to the Permissions tab > Bucket Policy editor.
Select Edit or Add bucket policy.
Replace the s3-bucket-name in the following JSON code with the exact name of the bucket you have set up.
Paste the updated code into the Bucket Policy editor and save changes.
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "Dotdigital Personalization S3 bucket link",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::854654557800:root"
},
"Action": [
"s3:ListBucket",
"s3:PutObject",
"s3:DeleteObject",
"s3:GetObject",
"s3:GetObjectTagging",
"s3:PutObjectTagging",
"s3:GetBucketLocation"
],
"Resource": [
"arn:aws:s3:::s3-bucket-name",
"arn:aws:s3:::s3-bucket-name/*"
]
}
]
}
Contact us
Once you've completed the steps above, contact us so we can grant permissions to your dedicated bucket and enable it within the admin interface.
Files added to the bucket are imported into Personalization and then deleted—similar to the process used for secure FTP imports.
Ensure that your bucket’s Block Public Access settings do not conflict with the permissions granted in the bucket policy. You can find this setting in the Permissions tab of your bucket.