Connect API

Connect to S3Box with the S3 API

Use these values with any tool or library that supports Amazon S3.

Connection values

Endpointhttps://s3.th-ubn-1.avesta.co.th
Regiondefault
SignatureAWS Signature v4
Addressing stylepath-style

Get an access key

  1. Sign in to the S3 Console and click Create S3 Credentials (account owner) — the Secret Key is shown once
  2. The endpoint and current Access Key are under Settings → S3 connection
  3. Give each app or person its own sub-user key (Sub Users → ⋯ → Access Keys)
  4. If a secret leaks or is lost, click Rotate Secret Key and update every tool — the old key stops working immediately

S3 Console →

Connection examples

Replace <ACCESS_KEY>, <SECRET_KEY> and <BUCKET_NAME> with your values. Never put keys in published code — read them from environment variables.

aws configure set aws_access_key_id <ACCESS_KEY>
aws configure set aws_secret_access_key <SECRET_KEY>
aws configure set default.region default
aws configure set default.s3.addressing_style path
aws configure set default.request_checksum_calculation when_required
aws configure set default.response_checksum_validation when_required

aws --endpoint-url https://s3.th-ubn-1.avesta.co.th s3 ls
aws --endpoint-url https://s3.th-ubn-1.avesta.co.th s3 mb s3://<BUCKET_NAME>
aws --endpoint-url https://s3.th-ubn-1.avesta.co.th s3 cp backup.zip s3://<BUCKET_NAME>/
aws --endpoint-url https://s3.th-ubn-1.avesta.co.th s3 sync ./data s3://<BUCKET_NAME>/data/

Recent AWS SDK/CLI versions send new checksums on every request, so the examples set them to "when required" for reliable use with S3-compatible storage (the Python example needs boto3 1.36 or newer; on older versions remove the two checksum lines).

Good to know

  • The Secret Key is shown once and cannot be viewed again
  • Always use HTTPS (the endpoint is https)
  • For data that must never be changed or deleted, enable Object Lock when creating the bucket

Having trouble connecting? Contact our team

Contact