> For the complete documentation index, see [llms.txt](https://docs.eazybackup.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eazybackup.com/e3-object-storage/getting-started/connection-details.md).

# Connection details

S3 endpoint, region, HTTPS, and where to find Access Keys for e3 Object Storage.

Use these settings in any S3-compatible client, script, or backup product.

## Required settings

| Setting                    | Value                                             |
| -------------------------- | ------------------------------------------------- |
| **Endpoint / Service URL** | `s3.ca-central-1.eazybackup.com`                  |
| **Region**                 | `ca-central-1`                                    |
| **Protocol**               | HTTPS (TLS)                                       |
| **Addressing style**       | Virtual-hosted (default for AWS CLI profile `e3`) |

Full URL for many tools: `https://s3.ca-central-1.eazybackup.com`

## Credentials

| Identity      | Where to get keys                                                                                             |
| ------------- | ------------------------------------------------------------------------------------------------------------- |
| **Root user** | **e3 Object Storage → Access Keys** — one key pair; create or rotate here.                                    |
| **Users**     | **e3 Object Storage → Users** → **Manage** → **Create access key** (or rotate Root from Users list for Root). |

Each key pair includes:

* **Access Key ID** (hint shown in the UI after creation)
* **Secret Access Key** (shown **once** at creation or rotation)

{% hint style="warning" %}
Keys only work for the **user that owns them**. A Root user key cannot access a User’s buckets, and a User key cannot access Root or another User’s buckets.
{% endhint %}

## Account ID (for bucket policies)

For JSON bucket policies, you need the **Account ID** shown on **Access Keys** and **Users** (tenant ID). Policies use principals like:

`arn:aws:iam::ACCOUNT_ID:user/USERNAME`

See Bucket policies.

## AWS CLI quick profile

```bash
aws configure --profile e3
# Access Key ID: your e3 access key
# Secret Access Key: your e3 secret key
# Region: ca-central-1

aws configure set s3.addressing_style virtual --profile e3
```

Full examples: AWS CLI v2 and s3cmd.

## Troubleshooting connection errors

| Symptom                  | Check                                                                                        |
| ------------------------ | -------------------------------------------------------------------------------------------- |
| `InvalidAccessKeyId`     | Key revoked or wrong user; create a new key for the bucket owner.                            |
| `SignatureDoesNotMatch`  | Wrong secret; secrets cannot be re-fetched from the UI.                                      |
| `AccessDenied` on bucket | Key user does not own the bucket; use the owner’s keys or create the bucket under that user. |
| SSL errors               | Use HTTPS and the hostname above, not a bare IP.                                             |