Create your first key and bucket

Step-by-step: create a Root access key, create a bucket, and optionally upload a file in the Bucket Browser.

This walkthrough gets you from a new e3 Object Storage service to a working bucket you can use with S3 clients.

You need an active e3 Object Storage service in the client area. If you are signing up for the first time, complete product selection and provisioning from Welcome page.

1

Sign in and open e3 Object Storage

1. Sign in at accounts.eazybackup.ca.

2. From the eazyBackup sidebar navigation, Open e3 Object Storage.

3. Confirm you see the object storage pages: Dashboard, Buckets, Access Keys, Users, Billing, Historical Stats.

2

Copy the Service URL

1. Open Access Keys.

2. Copy Service URL (s3.ca-central-1.eazybackup.com). You will need this endpoint ifor you S3 client.

See Connection details for region and HTTPS notes.

3

Create your Root access key

1. On Access Keys, click Create your first key (or Create new key if you are rotating).

2. Confirm with your account password when prompted.

3. Copy the Access Key ID and Secret Access Key immediately.

The secret key is shown only once. Store it in a password manager or secrets vault. You cannot view it again from the dashboard.

Rotating the Root key revokes the previous secret immediately. Update every app that used the old key.

4

Create a bucket

1. Open Buckets.

2. Click Create Bucket.

3. In the modal:

   • Bucket Name — globally unique name (lowercase letters, numbers, hyphens).

   • Select Bucket Owner — Root user for your first bucket, or a User you created under Users.

   • Enable Versioning — optional; keeps object versions for recovery.

   • Enable Object Locking — optional; immutability for compliance backups. Only enable Set a default retention policy if you understand the retention impact (see Versioning and Object Lock).

4. Click Create Bucket.

5

(Optional) Upload a test file

1. On Buckets, click Browse on your new bucket (requires a key for that bucket owner).

2. Use Upload or drag files into the upload area.

3. Confirm the object appears in the listing.

You can also verify with AWS CLI — see AWS CLI and s3cmd.

Next steps

• Additional identities — Users for separate buckets and scoped keys.

• Billing — How billing works explains peak storage and egress.

• Integrations — Connect apps and tools.