# Profiler Retention with AWS

Add the necessary AWS S3 configuration to store profiles to the `config` section of the `custom-values.yaml` file.

```yaml
    config: |
      storage:
        backend: s3 (1)
        s3:
          bucket_name: your-aws-s3-bucket (2)
          region: your-aws-region (3)
          endpoint: s3.us-west-2.amazonaws.com (4)
          access_key_id: "your-aws-access-key" (5)
          secret_access_key: "your-aws-secret-key" (6)
          insecure: true (7)
```

|     |     |
| --- | --- |
| **1** | `backend`: Set to `s3`. |
| **2** | `bucket_name`: Name of your S3 bucket |
| **3** | `region`: AWS region where your bucket is located |
| **4** | `endpoint`: S3 endpoint for your region |
| **5** | `access_key_id`: Your AWS access key ID |
| **6** | `secret_access_key`: Your AWS secret access key |
| **7** | `insecure`: Set to `true` if using HTTP instead of HTTPS. We recommend that you use the value of `false` for production clusters.