> For the complete documentation index, see [llms.txt](https://developers.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.didomi.io/integrations/generic-integrations/batch-export/destinations/aws-s3-bucket.md).

# AWS S3 Bucket (owned by Didomi)

We create a dedicated bucket for your organization and a role for delegating access to your AWS account. To access the exported data, you will need to assume the role created in our organization.

The bucket is configured with "[Requester Pays](https://docs.aws.amazon.com/AmazonS3/latest/dev/RequesterPaysBuckets.html)". Didomi will bear the cost of storing the exported data but the cost of requests and data download will be born by the AWS account requesting data.

The name of the AWS S3 bucket is as follows: `didomi-exports-{organization-id}-{random string}`

The ARN of the AWS role to access the bucket has the format: `arn:aws:iam::{didomi-aws-account-id}:role/{bucket-name}-role`

## Storage duration

The exported data is stored for 7 days. After 7 days, files are automatically deleted from the S3 bucket.\
If you want to keep data for more than 7 days, you will need to copy them to your own storage system.

## Configuration

You will need to provide the ID of the AWS account that you will use to access the S3 bucket containing your exported data


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.didomi.io/integrations/generic-integrations/batch-export/destinations/aws-s3-bucket.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.