Workaround for s3cmd Showing ETag as MD5 Sum
Coming from another cloud?
▸Azure·Blob lifecycle management
Blob lifecycle management
- Azure supports automated tiering (hot/cool/cold/archive) and expiration rules based on age, access time; Quake AI Swift S3 API lacks native lifecycle management per official OpenStack docs and no Quake AI-specific extension found.
- Azure policies apply account-wide or filtered by prefix/tags; Swift requires external cron/object-expirer daemon for deletes, no built-in tiering.
- Azure charges for tiering API calls; Swift has no equivalent billing as feature missing.
Workaround for s3cmd showing ETag as MD5 sum
Issue#
A known issue exists with the command-line application s3cmd, where s3cmd information incorrectly shows the ETag as an MD5 sum.
Sometimes the MD5 and ETag match, but for multipart objects the values differ.
See also: https://github.com/s3tools/s3cmd/issues/1336.
Workaround#
To view the ETag of an object, use the AWS CLI instead of s3cmd.
For example:
aws s3api head-object --bucket YOUR_BUCKET_NAME --key YOUR_OBJECT_NAME --query ETag --output textOr, to list all objects and relevant information in a bucket:
aws s3api list-objects --bucket YOUR_BUCKET_NAMEIn the example above, the key value is the object name.
To set up the AWS CLI, configure the config and credentials files with the following updates:
~/.aws/config
[default]
endpoint_url = https://object.us-east-1.rumble.cloud
region = local~/.aws/credentials
[default]
aws_access_key_id = YOUR_ACCESS_KEY
aws_secret_access_key = YOUR_SECRET_KEYAfter you update these two files, the tool works for S3 API subcommands.
Usage Guidelines
The sample code, software libraries, command line tools, proofs of concept, templates, and other related technology on this page (including any of the foregoing that is provided by Quake AI personnel) is provided to you as Quake AI Content under the Quake AI Customer Agreement, or the relevant written agreement between you and Quake AI (whichever applies). Do not use this Quake AI Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the Quake AI Content (such as sample code) as appropriate for production grade use based on your specific quality control practices and standards. Deploying Quake AI Content may incur Quake AI charges for creating or using Quake AI chargeable resources, such as running Compute instances or storing data in Object Storage. Your use is also subject to the Acceptable Use Policy.
For the full policy, see Usage Guidelines.
Last validated: 04.06.2026