Will my backup tool write to it?

Yes, if it can write to an S3-compatible target. Change the endpoint, add an access key, and it writes to Watad.

We test against the AWS CLI, rclone and restic. Veeam Backup & Replication, Synology Hyper Backup and Duplicati connect through their S3-compatible option.

Connect a client

export AWS_ACCESS_KEY_ID=<access-key-id>
export AWS_SECRET_ACCESS_KEY=<secret>
export AWS_DEFAULT_REGION=us-east-1

aws --endpoint-url https://s3.amanahcloud.bh \
  s3 cp ./backup.tar s3://<bucket>/backups/

Replace the values in angle brackets. Clients ask for a region: use us-east-1.

Where is the data kept?

In the Kingdom of Bahrain. Your objects are stored on servers inside the country, and you reach them at one endpoint.

S3 tools also ask for a region name. That is a label the tools expect, not a place: use us-east-1.

Stored inKingdom of Bahrain
S3 endpointhttps://s3.amanahcloud.bh
Consoleapp.amanahcloud.bh
Region name the tools ask forus-east-1

What does it cost to get my data back?

Nothing. There are no egress fees: restoring, downloading and reading your data carry no charge, however often you do it.

Storage itself is charged. The rate is not published here.

Taking data outEgress fee
Restore a backupNone
Download an objectNone
Copy a whole bucket outNone

Who can reach a bucket?

Only the people and keys you allow. A bucket is private unless you make it public.

Give each backup job its own key, scoped to one bucket with only the permissions it needs, so a leaked key reaches nothing else. People can protect their console sign-in with an authenticator code, and everyone in an organisation has a role: owner, admin or member.

Sample key
Namebackup-job-clinic
Bucketclinic-backups
CanRead, write and list objects
Cannot reachAny other bucket

What is not there yet?

Some things S3 users ask about are not in Watad today. We would rather you find out here than in the middle of a migration.

Not in Watad todayWhat to do
Retention locks and legal holdPlanned with Hisn.
Encryption at rest by defaultPlanned with Hisn. Until then, encrypt in your backup tool.
Replication between bucketsNot offered.
Single sign-onNot offered.
S3 ACLs, IAM and STSAccess is by scoped keys, plus a public-read policy for a bucket.
Bucket notificationsNot offered.

How do I start?

In three steps. The connection guide then checks each one with you.

  1. Sign up

    Create an account in the console at app.amanahcloud.bh.

  2. Create a bucket and a key

    Make a bucket, then open Keys and create an application key scoped to that bucket.

  3. Point your tool at the endpoint

    Set the endpoint to https://s3.amanahcloud.bh and the region to us-east-1, then run the first backup.