Skip to main content

Send scheduled exports to your own S3 bucket

Deliver exports directly into your AWS S3 bucket so they can feed your data warehouse or downstream pipeline.

Written by Stateable

Send exports straight to your own S3 bucket: if your team needs the files to land there — so they can feed a data warehouse, an internal dashboard, or another system you run — set up an external S3 destination. Once it's connected, any scheduled export can send its files to your bucket.

Only admins can set this up. If you don't see the Integrations tab inside the Exports sheet, your account doesn't have the Organization Settings permission. Ask a teammate who does.

What you'll need

  • An S3 bucket in your AWS account.

  • A prefix (the folder path inside the bucket) where Stateable should put the files. Example: stateable/commissions/.

  • An IAM user or role (the AWS login Stateable will use) with s3:PutObject permission on that folder.

  • An access key ID and secret access key for that login.

  • The bucket's AWS region.

Configure the destination

  1. Click Export and open the Integrations tab.

  2. Fill in the S3 form: bucket name, prefix, region, access key ID, and secret access key.

  3. Click Test Connection. Stateable writes a tiny test file to the folder and reads it back to make sure everything works. You'll see a success or failure banner.

  4. Save. You can now pick this destination when you create or edit a scheduled export.

Use the destination on a schedule

  1. Open the Scheduled Export tab.

  2. Create or edit a schedule, and choose Your S3 bucket as the destination.

  3. Save. The next run will send the files straight to the folder you set up.

Security notes

  • Your keys are stored encrypted and kept in Stateable's secrets manager. They never show up in our logs.

  • Use a dedicated IAM user that can only reach this one folder. Don't use your AWS root keys or a login that has access to everything.

  • Replace your access keys once a year, then update the integration with the new ones. Use Test Connection afterward to confirm it still works.

Troubleshooting

  • Test Connection fails with Access Denied — make sure the IAM login has s3:PutObject and s3:GetObject permission on the exact folder you entered.

  • Test Connection fails with NoSuchBucket — double-check that the bucket name and region match what you see in your AWS console.

  • Scheduled export ran but the file isn't in the bucket — check the prefix. If you left the slash off the end, the file can land one folder higher than you expected.

Troubleshooting

  • My IAM credentials are being rejected. The access key doesn't have s3:PutObject permission on the bucket. Add that permission to your IAM policy. See the AWS docs for bucket-policy examples.

  • Files arrive but the other system doesn't pick them up. The folder the files land in doesn't match the folder that system is watching. Check the prefix in the schedule's destination settings.

Get help

Still need a hand? Start a conversation from the Support button in the app, or email [email protected]. We reply within one business day for most tickets.

Related articles

Last reviewed: 2026-05-27

Did this answer your question?