> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/enterprise/self-hosted-secoda/additional-resources/additional-environment-variables/aws-bucket-with-access-keys-on-premise.md).

# AWS Bucket with Access Keys (on-premise)

### **Step 1: Log In to AWS Management Console**

1. Go to the [AWS Management Console](https://aws.amazon.com/console/).
2. Log in with your AWS credentials.

***

### **Step 2: Create an S3 Bucket**

1. In the AWS Management Console, search for **S3** in the search bar and select the **S3 service**.
2. Click on **"Create bucket"**.
3. Provide a **unique bucket name.**
4. Configure settings:
   * **Object Ownership**: Choose disabled.
   * **Block Public Access Settings**: Block public access.
5. Enable encryption and versioning.
6. Click **"Create bucket"**.

***

### **Step 3: Create Access Keys**

#### **A. Go to the IAM Console**

1. In the AWS Management Console, search for **IAM** (Identity and Access Management).
2. Click on **Users** in the IAM dashboard.

#### **B. Create or Select a User**

1. If creating a new user:
   * Click **"Add users"**.
   * Provide a username.
   * Select **"Programmatic access"** as the access type.
2. If using an existing user, click on the user name to edit their permissions.

#### **C. Attach Policies**

1. Assign a policy that allows access to S3, such as:
   * **Custom Policy**: Create a custom policy to restrict access to specific buckets or actions:

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

#### **D. Generate Access Keys**

1. Go to the **Security Credentials** tab for the user.
2. Click **"Create access key"**.
3. Copy and securely store the **Access Key ID** and **Secret Access Key**.
   * These keys will not be shown again after creation.

#### **Security Best Practices**

* Regularly rotate access keys.
* Use least privilege policies to limit access.


---

# 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.secoda.co/enterprise/self-hosted-secoda/additional-resources/additional-environment-variables/aws-bucket-with-access-keys-on-premise.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.