> For the complete documentation index, see [llms.txt](https://docs.kaiko.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaiko.com/cloud-delivery/getting-started/aws-s3.md). # AWS S3 How to receive our data through AWS 1. You will need to have access to an AWS account, which can be created [here](https://aws.amazon.com/resources/create-account/) 2. You will also need to retrieve your **AWS account ID** (or the specific ARNs of the accounts to give access to), the instructions regarding this step can be found [here](https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-identifiers.html). 3. Your AWS account ID (or ARNs) should be sent to . 4. Our team will then give you access to the data and will contact you to confirm the details. If you have any questions regarding this process, you can contact . --- # 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://docs.kaiko.com/cloud-delivery/getting-started/aws-s3.md?ask=&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.