# Workaround for s3cmd Showing ETag as MD5 Sum

Source: https://docs.quake.ai/docs/operate/troubleshooting/s3cmd-etag-workaround
Markdown: https://docs.quake.ai/docs/operate/troubleshooting/s3cmd-etag-workaround.md

---

# 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](https://github.com/s3tools/s3cmd/issues/1336).

## Workaround

To view the ETag of an object, use the AWS CLI instead of s3cmd.

For example:

```bash
aws s3api head-object --bucket YOUR_BUCKET_NAME --key YOUR_OBJECT_NAME --query ETag --output text
```

Or, to list all objects and relevant information in a bucket:

```bash
aws s3api list-objects --bucket YOUR_BUCKET_NAME
```

In 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`

```ini
[default]
endpoint_url = https://object.us-east-1.rumble.cloud
region = local
```

`~/.aws/credentials`

```ini
[default]
aws_access_key_id = YOUR_ACCESS_KEY
aws_secret_access_key = YOUR_SECRET_KEY
```

After you update these two files, the tool works for S3 API subcommands.