You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This stops the sync and revokes access to the destination.
229
+
230
+
## S3 Export
231
+
232
+
S3 Export delivers your data as an Iceberg table in a Dune-managed S3 bucket. Dune adds a bucket policy to the export bucket which grants an AWS principal you control read access. You can either:
233
+
234
+
- create an IAM role in your own AWS account with read access to S3 and give Dune that role's ARN, so only that role can read the bucket; or
235
+
- give Dune just your AWS account ID, and Dune grants the whole account access. You can then control which IAM users/roles have access to the S3 bucket by setting the appropriate IAM policy permissions.
236
+
237
+
You query the data directly from S3 with your own engine (e.g. Athena, Spark, DuckDB, etc.) using that principal, without going through Dune. S3 Export currently supports the **Iceberg** table format. To set up an S3 target, contact Dune with the bucket region you want, and either the IAM role ARN or the AWS account ID to grant read access.
238
+
239
+
Note that the bucket will be configured with [requester pays](https://docs.aws.amazon.com/AmazonS3/latest/userguide/RequesterPaysBuckets.html), so to read the data you have to set a header on the S3 requests to accept that you will be charged for read requests. Most AWS SDKs have a way to just configure this directly without having to manually set request headers.
0 commit comments