Data Delivery Using S3

Our preferred mode of delivery is through Amazon's AWS S3 service.

To set up this delivery, do the following:

  1. Sign into the AWS S3 console.
  2. Create a bucket for deliveries (for example, s3://YOURCOMPANY-data-deliveries).
    1. If you are using an existing bucket, ensure that Requester Pays is disabled.
  3. Modify the bucket policy in the Permissions tab.
  4. Paste the following into your permissions and replace {{your bucket name}} with your new bucket name (for example, YOURCOMPANY-data-deliveries) and click Save.
    "Version": "2012-10-17",
    "Statement": [
            "Sid": "People Data Labs Bucket Permissions",
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::556708831556:role/pdl-customer-deliveries"
            "Action": [
            "Resource": [
                "arn:aws:s3:::{{your bucket name}}",
                "arn:aws:s3:::{{your bucket name}}/*"
  1. Email [email protected] with your bucket URL.

Note on S3 Saving

When you click Save on the Bucket Policy page, AWS may not provide a "Saved" notification message and may also display the following:

This is a standard AWS message but for some it can be confusing. To confirm the new policy above is saved, refresh the page and check if the policy is still there.

Note on Data Delivery & IAM

Per best practices, we do not support the use of IAM users for data delivery. IAM users utilize Access Keys / Secret Access Keys and would need to be rotated regularly. The best practice is to use roles with the policy described above, which allows our PDL role to deliver the data to you.