AWS CLI
The AWS CLI is Amazon’s command-line tool for S3. With a separate zata profile, you can list, upload, download and share files in your Zata buckets, and keep your AWS settings untouched.
Before you start
- A bucket. See Create a bucket.
- An access key and secret key from the same region as the bucket. See Access keys.
- AWS CLI version 2.13 or newer. Check with
aws --version.
Connection settings
Install the AWS CLI
Linux (x86_64)
Windows, macOS, ARM Linux
Set up a Zata profile
These commands work the same in a Linux, macOS or Windows terminal. They save the settings in ~/.aws/config and ~/.aws/credentials (on Windows, in %USERPROFILE%\.aws\).
On AWS CLI versions older than 2.13, the profile cannot store the endpoint. Add --endpoint-url https://idr01.zata.ai to every command instead.
Test it
Replace my-bucket with your bucket name:
aws s3 ls --profile zata lists your buckets. A sub-user’s key shows no buckets there; use the bucket name directly.
Everyday commands
aws s3 cp uploads files larger than 8 MB in parts (multipart) by itself. aws s3 presign makes download links only; for upload links, use an SDK such as Python (boto3).
Test a multipart upload step by step
aws s3 cp does all of this by itself. Doing it by hand shows which step fails when another app cannot upload large files. Every part except the last must be at least 5 MB.
If the complete step fails, Zata removes that upload: start again with a new upload ID.
Unfinished uploads keep using storage until they are completed or cancelled. To find them:
A sub-user’s key may get AccessDenied on this list; the bucket owner’s key works.
If these steps work with the AWS CLI but another app still fails on large files, that app most likely sends the default checksums. See Tools built on the AWS SDK.
Troubleshooting
aws configure list --profile zata shows which keys and settings the profile really uses. For other errors, see Signature errors, Access denied and Wrong endpoint or region.
Never use --no-verify-ssl. Zata’s certificates are valid, so a certificate error points to a proxy or a wrong clock. See Network and certificates.