> For the complete documentation index, see [llms.txt](https://integrations.drivetrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.drivetrain.ai/integration-guide/integrate-with-drivetrain/others/integrating-with-amazon-s3.md).

# Integrating with Amazon S3

### Overview

This guide explains how customers can securely push data into Drivetrain’s Amazon S3 bucket.\
Drivetrain supports two integration methods:

1. **Access Key ID & Secret Access Key**
2. **Role-Based IAM Access**

Both methods allow you to upload files into a dedicated folder within Drivetrain’s S3 environment.

### Method 1: Integration Using Access Key ID & Secret Key

#### Required Information

Your Drivetrain integration team will provide the following:

* S3 Bucket Name: `dt-helm42`
* Folder Path: `dt-helm42/XXX`
* **AWS Access Key ID** & **Secret Access Key**

#### How to Use This Method

1. Configure your system, ETL tool, or script with:
2. Access Key ID
3. Secret Access Key
4. Bucket name
5. Folder path
6. Upload your files to the S3 folder exactly as shared by Drivetrain.

### Method 2: Integration Using Role-Based IAM

This method avoids storing long-lived keys and is the preferred, more secure option.

#### Required Information

To enable role-based access, you must provide Drivetrain with your:

* **AWS Account ID**

Drivetrain will then:

1. **Whitelist your AWS account**
2. **Create an IAM role** that your account is allowed to assume
3. **Grant that role permissions** to upload files into your designated S3 folder

#### How to Use This Method

1. Provide Drivetrain with your AWS Account ID.
2. Drivetrain will share:
   1. **S3 Bucket Name:** `dt-helm42`
   2. **Folder Path:** `dt-helm42/XXX`
3. Configure your system to:
   1. **Upload files** to the designated folder path


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://integrations.drivetrain.ai/integration-guide/integrate-with-drivetrain/others/integrating-with-amazon-s3.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.