...
Tip: add multiple profiles besides [default] that use different Swarm clusters or domains then refer to it using aws --profile devswarm …. Unfortunately the domain, which must resolve to your Gateway S3 endpoint, must always be specified on the command-line with --endpoint-url.
Increase the part size from the default (https://docs.aws.amazon.com/cli/latest/topic/s3-config.html#multipart-chunksize) 8MB to 100MB to improve read performance. This configures ~/.aws/config.
| Code Block |
|---|
aws configure set default.s3.multipart_chunksize 100MB |
This will show the buckets in your domain then list a bucket:
| Code Block |
|---|
aws s3api --endpoint-url http://mydomain.example.com:8090 list-buckets aws s3api --endpoint-url http://mydomain.example.com:8090 list-objects --bucket mybucket |
The aws s3 syntax is slight different than the aws s3api commands:
| Code Block |
|---|
aws s3 --endpoint-url http://mydomain.example.com:8090 ls aws s3 --endpoint-url http://mydomain.example.com:8090 ls s3://mybucket |
Tip: use aws --debug to see full HTTP request and response details, including the request-id for searching cloudgateway_server.log. Long listings might require --cli-read-timeout 300. Internal error messages like this are expected and can be ignored:botocore.exceptions.ConnectTimeoutError: Connect timeout on endpoint URL: "http://169.254.169.254/latest/meta-data/placement/availability-zone/"
...