> For the complete documentation index, see [llms.txt](https://docs.finleycms.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finleycms.com/core-capabilities/data-integrations/aws-s3-setup-guide.md).

# AWS S3 Setup Guide

## Overview

Finley uses AWS S3 data transfer to take in customer asset tapes on a regular cadence. This guide walks you through our preferred data transfer setup.

## Step-by-step instructions

The three steps to setting up an S3 transfer with Finley are:

1. **Give Finley your AWS account ID**. Finley will create an S3 bucket with cross-account permissions to your account, and let you know the name of the bucket (referenced onwards as \[cross-account-bucket-name]). 
2. **Confirm that your AWS account has access.** Once the bucket has been created, an admin user will be able to access the bucket via CLI (`aws s3 ls s3://[cross-account-bucket-name] --profile [admin-aws-profile]`). 
3. **You are now able to give your AWS service access to this S3 bucket through an IAM role with appropriate bucket permissions.** Example policy below:

```
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "s3:PutObject"
            ],
            "Resource": [
                "arn:aws:s3:::[cross-account-bucket-name]",
                "arn:aws:s3:::[cross-account-bucket-name]/*"
            ],
            "Effect": "Allow"
        }
    ]
}
```

And that's it! Once configured, the Finley team will provide additional guidance on preferred CSV data formats, and you’ll be able to programmatically drop CSV files into the bucket that we would incorporate into the required reports for capital provider submission.

## Uploading files after setup

Once the bucket is live, you will be able to upload files to it that Finley will now have access to. AWS has a suite of API and CLI tools to get this job done outlined [here](https://docs.aws.amazon.com/AmazonS3/latest/API/Type_API_Reference.html).


---

# 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://docs.finleycms.com/core-capabilities/data-integrations/aws-s3-setup-guide.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.