Use a scheduled query export to send a file from Slate to an Amazon Web Services (AWS) Simple Storage Service (S3) bucket. Configure the bucket endpoint and credentials in the query's Schedule Export settings.
Before you begin, build and test the query that produces the data you want to export. See Building a Data Export Query.
Before you begin
Obtain the following information from your AWS administrator:
The S3 bucket name and its regional endpoint.
An access key ID and secret access key with the permissions required to write to the bucket.
Any network or bucket policy restrictions that affect access from Slate.
🔑 To configure a scheduled export, you need the Administrator (All Access) role or the SFTP Access permission.
Configuring the export
In Queries / Reports, open the query and select Edit Query.
Select Schedule Export.
Set Destination to Custom File Transfer.
In Connection, enter the S3 connection string in this format:
s3://ACCESS_KEY_ID:SECRET_ACCESS_KEY@s3.REGION.amazonaws.com/BUCKET_NAME
Replace the placeholders with your credentials, the regional endpoint for your bucket, and the bucket name. For example, an endpoint in US East (N. Virginia) uses s3.us-east-1.amazonaws.com. Protect the connection string because it contains credentials.
In Path, enter the file name, such as
query.csv. Include the file extension required by the receiving process.Set Format and the other file settings to match the receiving process.
Set Notification to alert the appropriate recipients if the export fails.
Select the requested delivery window and weekdays.
Set Status to Active when the query and destination are ready for scheduled delivery.
Select Save.
For more information about the file settings, delivery windows, and path variables, see Scheduling Data Exports.
Troubleshooting exports to AWS S3
Test with a limited set of data. Confirm that the file appears in the intended bucket and path and that its contents and format meet the receiving process requirements.
Review the scheduled job in Database → Job Activity Monitor and check any failure notifications. If the transfer fails:
Check the regional endpoint, bucket name, access key ID, and secret access key.
Confirm that the credentials have the required bucket permissions and that bucket or network restrictions permit the connection.
URL-encode reserved characters in the credential values in the connection string. For example, encode a slash (
/) in the secret access key as%2F.