> For the complete documentation index, see [llms.txt](https://docs.mikopbx.com/mikopbx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mikopbx.com/mikopbx/english/manual/maintenance/storage/aws.md). # Connecting AWS S3 Storage ### Creating a Bucket 1. Go to the AWS console ([link](https://console.aws.amazon.com/)). Navigate to **"All services"** -> **"Storage"** -> **"S3"**.

2. Click **"Create bucket"**.

3. Enter any name for the bucket (field **"Bucket name"**). Leave all other parameters as default and click **"Create bucket".**

### Creating an IAM User and Access Keys 1. Go to **"All services"** -> **"Security, Identity, & Compliance"** -> **"IAM"**.

2. Next, create a new IAM user. Go to the **"Access Management"** tab, then **"Users"**. Click **"Create user"**.

3. Enter the name of the IAM user in the **"User name"** field. Click **"Next"**.

4. Select **"Attach policies directly"** as the **"Permissions options"**. Scroll down the page.

5. In the **"Permissions policies"** section click **"Create policy"**.

6. In the newly opened tab, in the **"Policy editor"**, select **"JSON"** as the format and paste the following content into the parameters field: ```json { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "s3:PutObject", "s3:GetObject", "s3:DeleteObject", "s3:ListBucket" ], "Resource": [ "arn:aws:s3:::your-bucket-name", "arn:aws:s3:::your-bucket-name/*" ] } ] } ``` {% hint style="warning" %} Replace **"your-bucket-name"** with the name of the bucket you created earlier (in this guide — **"aws-s3-mikopbxstorage"**). {% endhint %} Click **"Next"**.

7. Next, specify any name for the policy being created. Click **"Next"**.

8. Return to the user creation tab, refresh the policy list, and select the previously created policy (in this guide — **"access-mikopbx"**). Click **"Next"**.

9. Confirm user creation: click **"Create user"**.

10. Open the page of the created user by clicking on the username.

11. Go to the **"Security credentials"** section. Click **"Create access key"**.

12. Select **"Application running outside AWS"**. Click **"Next"**.

Selecting parameters when creating the key

13. Enter a description for the key so that you can identify it later. Click **"Create access key"**.

The **Access key** and **Secret access key** will be displayed. Save them — they will be needed later when configuring MikoPBX. {% hint style="warning" %} The secret access key can only be viewed or downloaded now. It cannot be recovered later. {% endhint %}

### Connecting to MikoPBX 1. Go to the **"Maintenance"** -> **"Storage"** tab.

2. Open the **"S3 Cloud Storage"** tab and fill in the following fields: * **Automatic recording upload to cloud storage** — enable the switch. * **S3 endpoint URL** — enter the S3 AWS endpoint depending on the region of your bucket ([link](https://docs.aws.amazon.com/general/latest/gr/s3.html) to the table with all URLs). In this guide — `https://s3.ap-southeast-1.amazonaws.com` * **S3 region** — specify the **region of your bucket**. In this guide — `ap-southeast-1` * **S3 bucket name** — enter the name of the bucket created in AWS (for example `aws-s3-mikopbxstorage` in this guide) * **Access key** and **Secret key** — paste the values obtained when creating the service account access key. Configure the **“Local storage period (S3 mode)”** slider — choose how long recordings will be stored locally before being deleted after uploading to the cloud. {% hint style="info" %} Shorter local storage periods free up disk space faster. {% endhint %} Click **“Save”**.

Parameters for connecting S3 cloud storage in MikoPBX

After saving the settings, click **"Test connection"**. If the connection is successful, the message **“S3 connection successful”** will appear and synchronization of call recordings will begin.

--- # 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.mikopbx.com/mikopbx/english/manual/maintenance/storage/aws.md?ask=&goal= ``` `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.