Connect with the AWS CLI
Point the AWS CLI, boto3 or any S3 SDK at Z2 using the endpoint, region and access key from the console.
Z2 speaks the S3 API with AWS Signature Version 4. Any S3-compatible client works once it is given the right endpoint, region and credentials.
Get the connection details
Console → Z2 Storage → your plan → Connection:
- Endpoint — for example
https://z2.example-endpoint(copy yours) - Region — copy the value shown
- Access key — choose Show credentials to reveal the Key ID and Secret
The console's quick-start tabs show the same values filled in.
Environment variables
This is the least error-prone way to configure the CLI:
export AWS_ACCESS_KEY_ID="<key id>"
export AWS_SECRET_ACCESS_KEY="<secret>"
export AWS_ENDPOINT_URL="<endpoint from console>"
export AWS_DEFAULT_REGION="<region from console>"
Then every command uses the endpoint automatically:
aws s3 ls
aws s3 ls s3://my-bucket
aws s3 cp ./backup.tar.gz s3://my-bucket/backups/backup.tar.gz
aws s3 sync ./public s3://my-bucket/assets --delete
Per-command endpoint
If you prefer not to export the endpoint:
aws s3 ls --endpoint-url "<endpoint from console>"
aws s3 cp report.pdf s3://my-bucket/reports/report.pdf --endpoint-url "<endpoint from console>"
Named profile
Keep a profile in ~/.aws/config:
[profile z2]
region = <region from console>
endpoint_url = <endpoint from console>
s3 =
addressing_style = path
And credentials in ~/.aws/credentials:
[z2]
aws_access_key_id = <key id>
aws_secret_access_key = <secret>
Use it with aws s3 ls --profile z2.
Path-style addressing
Z2 is path-style only: the bucket is the first path segment (https://endpoint/bucket/key). It does not use virtual-hosted-style (https://bucket.endpoint/key).
Most SDKs default to virtual-hosted style for AWS endpoints. Set path style explicitly:
- AWS CLI —
s3.addressing_style = pathin the profile, or--endpoint-urlwith newer CLI versions that detect custom endpoints. - boto3 —
config=Config(s3={"addressing_style": "path"}) - JavaScript SDK v3 —
forcePathStyle: true - rclone —
force_path_style = true
If requests return signature or host errors, path style is the first thing to check.
boto3
import boto3
from botocore.config import Config
s3 = boto3.client(
"s3",
endpoint_url="<endpoint from console>",
region_name="<region from console>",
aws_access_key_id="<key id>",
aws_secret_access_key="<secret>",
config=Config(s3={"addressing_style": "path"}),
)
print(s3.list_buckets()["Buckets"])
s3.upload_file("local.zip", "my-bucket", "backups/local.zip")
Presigned URLs
Presigned URLs work for GET and PUT. Generate them with the SDK; Z2 verifies the signature against your key.
url = s3.generate_presigned_url(
"get_object",
Params={"Bucket": "my-bucket", "Key": "reports/q3.pdf"},
ExpiresIn=300,
)
print(url)
Keep expiries short for private files. A presigned URL carries only your key's permissions and anyone holding it can use it until it expires.
What is not supported
- Bucket creation and deletion: use the console.
- Versioning, ACLs, object tagging and conditional requests.
- Virtual-hosted-style bucket addressing.
See Keys, quotas and limits for the full list.
Common errors
SignatureDoesNotMatch — wrong secret, wrong region, or the request was signed for a different host. Re-copy the credentials and endpoint.
AccessDenied — the key was rotated or the bucket belongs to another plan. Unknown buckets and other tenants' buckets return the same error on purpose.
QuotaExceeded — the bucket's quota is full. Delete objects or create a new bucket if the plan has unallocated capacity.
RequestTimeTooSkewed — the client clock is more than 15 minutes off. Fix NTP on the machine.
MethodNotAllowed on bucket delete — expected. Delete buckets in the console.
Next
- aws cli
- boto3
- sdk
- endpoint
- region
- signature v4
- s3
Ready to use this
S3-compatible buckets your existing tools already speak.
- No egress fees
- Per-bucket quotas from the console

