S3 storage, kept in Bahrain.
Watad speaks the S3 API, so the tools you already run can write to it.
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/# ~/.config/rclone/rclone.conf
[amanah]
type = s3
provider = Other
access_key_id = <access-key-id>
secret_access_key = <secret>
endpoint = https://s3.amanahcloud.bh
region = us-east-1
rclone sync /srv/data amanah:<bucket>/dataexport AWS_ACCESS_KEY_ID=<access-key-id>
export AWS_SECRET_ACCESS_KEY=<secret>
export AWS_DEFAULT_REGION=us-east-1
export RESTIC_REPOSITORY=s3:https://s3.amanahcloud.bh/<bucket>/restic
restic init
restic backup /srv/dataReplace 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 in | Kingdom of Bahrain |
|---|---|
| S3 endpoint | https://s3.amanahcloud.bh |
| Console | app.amanahcloud.bh |
| Region name the tools ask for | us-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 out | Egress fee |
|---|---|
| Restore a backup | None |
| Download an object | None |
| Copy a whole bucket out | None |
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.
| Name | backup-job-clinic |
|---|---|
| Bucket | clinic-backups |
| Can | Read, write and list objects |
| Cannot reach | Any 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 today | What to do |
|---|---|
| Retention locks and legal hold | Planned with Hisn. |
| Encryption at rest by default | Planned with Hisn. Until then, encrypt in your backup tool. |
| Replication between buckets | Not offered. |
| Single sign-on | Not offered. |
| S3 ACLs, IAM and STS | Access is by scoped keys, plus a public-read policy for a bucket. |
| Bucket notifications | Not offered. |
How do I start?
In three steps. The connection guide then checks each one with you.
Sign up
Create an account in the console at
app.amanahcloud.bh.Create a bucket and a key
Make a bucket, then open Keys and create an application key scoped to that bucket.
Point your tool at the endpoint
Set the endpoint to
https://s3.amanahcloud.bhand the region tous-east-1, then run the first backup.
