# Create an S3 Bucket on AWS

## Description

This is an example of how a bucket can be set up to allow specific domain(s) to upload, download, and delete objects to/from the bucket.

## Instructions

* Go to the AWS Console and choose `S3`
  * Type s3 on the search bar and the service will show up

![Untitled](/files/DSK05bsSQKexLT5ysR8j)

* Click on <mark style="color:red;">`Create Bucket`</mark>

<figure><img src="/files/t7QsTkldqoQfyLCTovde" alt=""><figcaption></figcaption></figure>

* Choose a unique bucket name (AWS will do the validation, and that involves ALL buckets from a given region, not only buckets associated to your account)
* Select an <mark style="color:red;">`AWS Region`</mark>
* On <mark style="color:red;">`Block Public Access settings for this bucket`</mark> leave unchecked only the box for **Block public and cross-account access to buckets and objects through any public bucket or access point policies**
* Click on <mark style="color:red;">`Create bucket`</mark>

<figure><img src="/files/eHRn3o2BpVQ56EFacd7u" alt=""><figcaption></figcaption></figure>

Once the bucket is created, select the newly created bucket and go to the <mark style="color:red;">`Permission`</mark> tab.

<figure><img src="/files/6qFgrkmf6F80FAkBDfqV" alt=""><figcaption></figcaption></figure>

* Scroll to the section <mark style="color:red;">`Cross-origin resource sharing (CORS)`</mark>

<figure><img src="/files/Yi1OskZCioI9AeFd3Jzg" alt=""><figcaption></figcaption></figure>

* Click on <mark style="color:red;">`Edit`</mark>, shown on image above, and you will be redirected to the following page.

<figure><img src="/files/qlydCeP4XOC1DKzW7Pij" alt=""><figcaption></figcaption></figure>

* Use a CORS configuration written in JSON, like the example below. More examples on CORS can be found on [AWS docs](https://docs.aws.amazon.com/AmazonS3/latest/userguide/ManageCorsUsing.html)

```bash
[
    {
        "AllowedHeaders": [
            "*"
        ],
        "AllowedMethods": [
            "PUT",
            "POST",
            "DELETE",
            "GET"
        ],
        "AllowedOrigins": [
            "https://my.example.com",
						"https://*.examples.com"
        ],
        "ExposeHeaders": [
            "x-amz-server-side-encryption",
            "x-amz-request-id",
            "x-amz-id-2"
        ],
        "MaxAgeSeconds": 3000
    }
]
```

> The example above shows an object that allows origins to upload (POST / PUT), download (GET), and delete (DELETE) objects. If one of these actions should not be allowed, remove them from the methods.

## Credentials needed for BetterForms

In order to be able to communicate with the bucket, we need to add the AWS access key and secret access key, it can be either an existing or newly created one.

* If a new one needs to be created, click on the account button located on the top right, and select <mark style="color:red;">`Security credentials`</mark>.

![](/files/vX1VWMq8Xi7f6v7pqz4S)

* Under the tab <mark style="color:red;">`AWS IAM credentials`</mark>, click on <mark style="color:red;">`Create Access key`</mark>. Download the .csv file with the secret key and save it on your local machine.

<figure><img src="/files/m86j6DMBIDHISRhU8Oyl" alt=""><figcaption></figcaption></figure>

Fields that will be needed for BetterForms to create a signed URL include:

* Host (ex. s3.amazonaws.com)
* Region (ex. us-west-1)
* Access Key
* Secret Access Key
* Bucket Name


---

# Agent Instructions: 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:

```
GET https://docs.klai.studio/reference/apis-and-services/integrations/create-an-s3-bucket-on-aws.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.