Composite checksum
A composite checksum is an object-level integrity value formed by combining the ordered checksums of the object's upload parts under a specified construction.
Amazon S3 distinguishes COMPOSITE from FULL_OBJECT. [1] For multipart SHA-256, its documented construction hashes the concatenated binary part digests and returns the Base64 digest with a part-count suffix; hashing the assembled file once is a different construction. [2]
Relations
- related
- checksum, full-object-checksum, multipart-upload, entity-tag, object-storage
Advantages
- Part checksums can be validated independently before their ordered digests are combined into the object's composite checksum. [2]
Limitations
- Verification requires the original part boundaries, part order and specified algorithm; a different multipart layout can change the value without changing the assembled bytes. [2]
- For S3 GetObject, request ChecksumMode ENABLED and inspect ChecksumType alongside the algorithm field; the ETag is a separate validator, not a substitute checksum. [3]
Citations
- Amazon S3: Checking object integrity for data uploads, full-object and composite checksum types
- Amazon S3 tutorial: Upload an object through multipart upload and verify its data integrity, step 9
- Amazon S3 API Reference: GetObject, checksum mode, checksum type and ETag