Home / Docs / Quick start

Developer quick start

Connect to disk.ie with the S3-compatible tools you already use. The same access key works for aws cli, rclone, restic and Cyberduck.

The endpoint

• S3 URL: https://s3.disk.ie
• Signing host: s3.disk.ie
• Region to send in the signature: us-east-1
• Auth: standard AWS Signature V4. You mint an access key from the dashboard at my.netquirk.com.

us-east-1 is the signing-region constant your client must send in the SigV4 canonical request — the same value every S3-compatible client expects. It is not a data-centre label.

Prerequisites

1. A disk.ie account. Sign in once via the account portal.
2. An access key. In the dashboard, open Account → Access keys and create one. The secret is shown once — copy it now.
3. A backup tool you trust. The examples below cover aws cli, rclone, restic and Cyberduck.

aws-cli

Configure a profile that points at https://s3.disk.ie:

[profile disk-ie]
aws_access_key_id = AKIAEXAMPLE
aws_secret_access_key = <paste-from-dashboard>
region = us-east-1
output = json

# Then list your buckets:
aws --profile disk-ie --endpoint-url https://s3.disk.ie s3 ls

# Or export the credentials and skip the profile:
AWS_ACCESS_KEY_ID=AKIAEXAMPLE \
AWS_SECRET_ACCESS_KEY='<paste-from-dashboard>' \
AWS_REGION=us-east-1 \
  aws --endpoint-url https://s3.disk.ie s3 ls s3://<bucket>

Pass --endpoint-url https://s3.disk.ie on every command so the SigV4 Host header is s3.disk.ie.

rclone

rclone treats https://s3.disk.ie as Other S3-compatible storage. Add a remote:

rclone config create disk-ie s3 \
  provider Other \
  endpoint https://s3.disk.ie \
  region us-east-1 \
  access_key_id AKIAEXAMPLE \
  secret_access_key "<paste-from-dashboard>" \
  no_check_bucket true

# Then:
rclone lsd disk-ie:
rclone sync ./backups disk-ie:backups

restic

restic speaks S3 with a few -o flags. The endpoint URL goes in the RESTIC_REPOSITORY:

export AWS_ACCESS_KEY_ID=AKIAEXAMPLE
export AWS_SECRET_ACCESS_KEY="<paste-from-dashboard>"

restic -o s3.bucket=<bucket> \
       -o s3.region=us-east-1 \
       -o s3.endpoint=https://s3.disk.ie \
       -o s3.layout=default \
       init

# Or via RESTIC_REPOSITORY:
RESTIC_REPOSITORY="s3:https://s3.disk.ie/<bucket>" \
  restic -o s3.region=us-east-1 -o s3.layout=default backup ./data

Cyberduck

Cyberduck is a graphical S3 client for macOS and Windows. Add a new connection:

1. Open Bookmark → Open Connection.
2. From the protocol dropdown, choose S3 (HTTP/HTML) Profile.
3. Set Server to s3.disk.ie.
4. Tick Use custom URL and enter https://s3.disk.ie.
5. Enter the Access Key ID from the dashboard.
6. Paste the Secret Access Key when prompted.
7. Click Connect. Your buckets appear in the browser window.

Drag-and-drop to upload or download files. Cyberduck computes the SigV4 signature against the Server value, which is why s3.disk.ie matters more than the connection URL.

Operations

List a bucket

aws --endpoint-url https://s3.disk.ie \
    s3 ls s3://backups/

rclone ls disk-ie:backups

restic -o s3.bucket=backups \
       -o s3.region=us-east-1 \
       -o s3.endpoint=https://s3.disk.ie \
       snapshots

Upload a single file

aws --endpoint-url https://s3.disk.ie \
    s3 cp ./photo.jpg s3://backups/photos/2026-10/photo.jpg

rclone copy ./photo.jpg disk-ie:backups/photos/2026-10/

Download a single file

aws --endpoint-url https://s3.disk.ie \
    s3 cp s3://backups/photos/2026-10/photo.jpg ./photo.jpg

rclone copy disk-ie:backups/photos/2026-10/photo.jpg ./

Restore a restic snapshot

RESTIC_REPOSITORY="s3:https://s3.disk.ie/backups" \
  restic -o s3.region=us-east-1 -o s3.layout=default \
         restore latest --target ./restore

Troubleshooting

• SignatureDoesNotMatch: the SigV4 Host header must be s3.disk.ie. aws-cli sends it automatically when you pass --endpoint-url https://s3.disk.ie; rclone and restic include it in the canonical request.
• 403 SlowDown: you are within the last 10 % of your plan's rate cap. Back off and retry, or move up a plan from the dashboard.
• 507 Insufficient Storage: the write would push you past the hard cap. Reduce the upload size or raise the cap in the dashboard.
• 404 Not Found on a key you uploaded: the object was deleted, or the bucket or key name has a typo. Re-upload from your backup tool if needed.
• Unknown error signing request: the access key is disabled or revoked. Create a fresh one from the dashboard and update the credentials in your backup tool.