Cloud Object Storage, Multipart Uploads, Presigned URLs and ETag Verification Across 54 Formats: Questions and Answers
Engineering reference answering 100 distinct technical questions on uploading, partitioning, tagging, and verifying all 54 file formats across Amazon S3, Google Cloud Storage, Azure Blob Storage, and S3-compatible object stores across all 54 file formats supported by SampleTestFiles.
Representative format hubs and diagnostic tools
Part 1: Document, spreadsheet and text format questions
- 1. What metadata headers and part-sizing rules should be used when uploading .avro (Avro) objects to S3 or GCS?
- Set Content-Type to application/avro, include x-amz-meta-sha256 with the 64-character hex digest (a53b9283c084120f… for sample-avro-1kb.avro), and for .avro objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 2. What metadata headers and part-sizing rules should be used when uploading .bin (BIN) objects to S3 or GCS?
- Set Content-Type to application/octet-stream, include x-amz-meta-sha256 with the 64-character hex digest (bb174eca55fcab7b… for sample-bin-1kb.bin), and for .bin objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 3. What metadata headers and part-sizing rules should be used when uploading .bmp (BMP) objects to S3 or GCS?
- Set Content-Type to image/bmp, include x-amz-meta-sha256 with the 64-character hex digest (d7833ceeb6df6a3f… for sample-bmp-10kb.bmp), and for .bmp objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 4. What metadata headers and part-sizing rules should be used when uploading .css (CSS) objects to S3 or GCS?
- Set Content-Type to text/css, include x-amz-meta-sha256 with the 64-character hex digest (d66dd341e097bfbf… for sample-css-1kb.css), and for .css objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 5. What metadata headers and part-sizing rules should be used when uploading .csv (CSV) objects to S3 or GCS?
- Set Content-Type to text/csv, include x-amz-meta-sha256 with the 64-character hex digest (cdddf7fab2967f74… for sample-csv-1kb.csv), and for .csv objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 6. What metadata headers and part-sizing rules should be used when uploading .docx (DOCX) objects to S3 or GCS?
- Set Content-Type to application/vnd.openxmlformats-officedocument.wordprocessingml.document, include x-amz-meta-sha256 with the 64-character hex digest (f035af1f12c5f378… for sample-docx-50kb.docx), and for .docx objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 7. What metadata headers and part-sizing rules should be used when uploading .eml (EML) objects to S3 or GCS?
- Set Content-Type to message/rfc822, include x-amz-meta-sha256 with the 64-character hex digest (fcb83c22ab1b25f4… for sample-eml-1kb.eml), and for .eml objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 8. What metadata headers and part-sizing rules should be used when uploading .epub (EPUB) objects to S3 or GCS?
- Set Content-Type to application/epub+zip, include x-amz-meta-sha256 with the 64-character hex digest (7aeb3a14b30fc59f… for sample-epub-10kb.epub), and for .epub objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 9. What metadata headers and part-sizing rules should be used when uploading .flac (FLAC) objects to S3 or GCS?
- Set Content-Type to audio/flac, include x-amz-meta-sha256 with the 64-character hex digest (7d5b1004d60d26ed… for sample-flac-100kb.flac), and for .flac objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 10. What metadata headers and part-sizing rules should be used when uploading .geojson (GeoJSON) objects to S3 or GCS?
- Set Content-Type to application/geo+json, include x-amz-meta-sha256 with the 64-character hex digest (9be0172ddbe0d3f7… for sample-geojson-1kb.geojson), and for .geojson objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 11. What metadata headers and part-sizing rules should be used when uploading .gif (GIF) objects to S3 or GCS?
- Set Content-Type to image/gif, include x-amz-meta-sha256 with the 64-character hex digest (66c85de4a8d004e4… for sample-gif-10kb.gif), and for .gif objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 12. What metadata headers and part-sizing rules should be used when uploading .gltf (glTF) objects to S3 or GCS?
- Set Content-Type to model/gltf+json, include x-amz-meta-sha256 with the 64-character hex digest (00005d45316577b7… for sample-gltf-1kb.gltf), and for .gltf objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 13. What metadata headers and part-sizing rules should be used when uploading .gpx (GPX) objects to S3 or GCS?
- Set Content-Type to application/gpx+xml, include x-amz-meta-sha256 with the 64-character hex digest (753bd5be3339a3bc… for sample-gpx-1kb.gpx), and for .gpx objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 14. What metadata headers and part-sizing rules should be used when uploading .gz (GZ) objects to S3 or GCS?
- Set Content-Type to application/gzip, include x-amz-meta-sha256 with the 64-character hex digest (d67bc6e2b98c4e46… for sample-gz-1kb.gz), and for .gz objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 15. What metadata headers and part-sizing rules should be used when uploading .html (HTML) objects to S3 or GCS?
- Set Content-Type to text/html, include x-amz-meta-sha256 with the 64-character hex digest (eabca5a92fca425f… for sample-html-1kb.html), and for .html objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 16. What metadata headers and part-sizing rules should be used when uploading .ico (ICO) objects to S3 or GCS?
- Set Content-Type to image/vnd.microsoft.icon, include x-amz-meta-sha256 with the 64-character hex digest (deterministic… for sample-ico-10kb.ico), and for .ico objects above 5 MB (up to 100 MB), use 8 MB or 16 MB multipart upload chunks.
- 17. What metadata headers and part-sizing rules should be used when uploading .ics (iCalendar) objects to S3 or GCS?
- Set Content-Type to text/calendar, include x-amz-meta-sha256 with the 64-character hex digest (b53dd9960c400e35… for sample-ics-1kb.ics), and for .ics objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 18. What metadata headers and part-sizing rules should be used when uploading .ini (INI) objects to S3 or GCS?
- Set Content-Type to text/plain, include x-amz-meta-sha256 with the 64-character hex digest (58c71755af8a90ba… for sample-ini-1kb.ini), and for .ini objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 19. What metadata headers and part-sizing rules should be used when uploading .jpg (JPG) objects to S3 or GCS?
- Set Content-Type to image/jpeg, include x-amz-meta-sha256 with the 64-character hex digest (8ee87ac7e59dde63… for sample-jpg-1kb.jpg), and for .jpg objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 20. What metadata headers and part-sizing rules should be used when uploading .js (JavaScript) objects to S3 or GCS?
- Set Content-Type to text/javascript, per RFC 9239, include x-amz-meta-sha256 with the 64-character hex digest (3555814484c57fa1… for sample-js-1kb.js), and for .js objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 21. What metadata headers and part-sizing rules should be used when uploading .json (JSON) objects to S3 or GCS?
- Set Content-Type to application/json, include x-amz-meta-sha256 with the 64-character hex digest (e6b79ec0b9d43a78… for sample-json-1kb.json), and for .json objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 22. What metadata headers and part-sizing rules should be used when uploading .jsonl (JSONL) objects to S3 or GCS?
- Set Content-Type to application/jsonl, include x-amz-meta-sha256 with the 64-character hex digest (c68974416de0b42c… for sample-jsonl-1kb.jsonl), and for .jsonl objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 23. What metadata headers and part-sizing rules should be used when uploading .kml (KML) objects to S3 or GCS?
- Set Content-Type to application/vnd.google-earth.kml+xml, include x-amz-meta-sha256 with the 64-character hex digest (405296fc546173a0… for sample-kml-1kb.kml), and for .kml objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 24. What metadata headers and part-sizing rules should be used when uploading .log (LOG) objects to S3 or GCS?
- Set Content-Type to text/plain, include x-amz-meta-sha256 with the 64-character hex digest (41cbef53cbcb07bf… for sample-log-1kb.log), and for .log objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 25. What metadata headers and part-sizing rules should be used when uploading .m4a (M4A) objects to S3 or GCS?
- Set Content-Type to audio/mp4, include x-amz-meta-sha256 with the 64-character hex digest (36b04a984c79c348… for sample-m4a-100kb.m4a), and for .m4a objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
Part 2: Image, audio, video, archive and 3D format questions
- 1. What metadata headers and part-sizing rules should be used when uploading .md (Markdown) objects to S3 or GCS?
- Set Content-Type to text/markdown, include x-amz-meta-sha256 with the 64-character hex digest (8c04ab877ffd78d2… for sample-md-1kb.md), and for .md objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 2. What metadata headers and part-sizing rules should be used when uploading .mkv (MKV) objects to S3 or GCS?
- Set Content-Type to video/x-matroska, include x-amz-meta-sha256 with the 64-character hex digest (bbd4d0d69f551e34… for sample-mkv-100kb.mkv), and for .mkv objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 3. What metadata headers and part-sizing rules should be used when uploading .mov (MOV) objects to S3 or GCS?
- Set Content-Type to video/quicktime, include x-amz-meta-sha256 with the 64-character hex digest (a79364ccad697070… for sample-mov-100kb.mov), and for .mov objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 4. What metadata headers and part-sizing rules should be used when uploading .mp3 (MP3) objects to S3 or GCS?
- Set Content-Type to audio/mpeg, include x-amz-meta-sha256 with the 64-character hex digest (f485bac1a1c6c218… for sample-mp3-100kb.mp3), and for .mp3 objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 5. What metadata headers and part-sizing rules should be used when uploading .mp4 (MP4) objects to S3 or GCS?
- Set Content-Type to video/mp4, include x-amz-meta-sha256 with the 64-character hex digest (60dec7b5883beb89… for sample-mp4-100kb.mp4), and for .mp4 objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 6. What metadata headers and part-sizing rules should be used when uploading .obj (OBJ) objects to S3 or GCS?
- Set Content-Type to model/obj, include x-amz-meta-sha256 with the 64-character hex digest (50571a2608db70d5… for sample-obj-1kb.obj), and for .obj objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 7. What metadata headers and part-sizing rules should be used when uploading .ods (ODS) objects to S3 or GCS?
- Set Content-Type to application/vnd.oasis.opendocument.spreadsheet, include x-amz-meta-sha256 with the 64-character hex digest (bef615f4c17ff3f9… for sample-ods-10kb.ods), and for .ods objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 8. What metadata headers and part-sizing rules should be used when uploading .odt (ODT) objects to S3 or GCS?
- Set Content-Type to application/vnd.oasis.opendocument.text, include x-amz-meta-sha256 with the 64-character hex digest (5d076b5d70f3b35c… for sample-odt-10kb.odt), and for .odt objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 9. What metadata headers and part-sizing rules should be used when uploading .pdf (PDF) objects to S3 or GCS?
- Set Content-Type to application/pdf, include x-amz-meta-sha256 with the 64-character hex digest (065325468ac444eb… for sample-pdf-5kb.pdf), and for .pdf objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 10. What metadata headers and part-sizing rules should be used when uploading .png (PNG) objects to S3 or GCS?
- Set Content-Type to image/png, include x-amz-meta-sha256 with the 64-character hex digest (7f4bf91380e02b39… for sample-png-1kb.png), and for .png objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 11. What metadata headers and part-sizing rules should be used when uploading .pptx (PPTX) objects to S3 or GCS?
- Set Content-Type to application/vnd.openxmlformats-officedocument.presentationml.presentation, include x-amz-meta-sha256 with the 64-character hex digest (57d931827d83c96d… for sample-pptx-100kb.pptx), and for .pptx objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 12. What metadata headers and part-sizing rules should be used when uploading .rtf (RTF) objects to S3 or GCS?
- Set Content-Type to application/rtf, include x-amz-meta-sha256 with the 64-character hex digest (7359e23a983cc8fe… for sample-rtf-1kb.rtf), and for .rtf objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 13. What metadata headers and part-sizing rules should be used when uploading .sql (SQL) objects to S3 or GCS?
- Set Content-Type to application/sql, include x-amz-meta-sha256 with the 64-character hex digest (c69482bb915813ee… for sample-sql-1kb.sql), and for .sql objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 14. What metadata headers and part-sizing rules should be used when uploading .srt (SRT) objects to S3 or GCS?
- Set Content-Type to application/x-subrip, include x-amz-meta-sha256 with the 64-character hex digest (854da70417fd63ce… for sample-srt-1kb.srt), and for .srt objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 15. What metadata headers and part-sizing rules should be used when uploading .stl (STL) objects to S3 or GCS?
- Set Content-Type to model/stl, include x-amz-meta-sha256 with the 64-character hex digest (6fc6b99eb04a89de… for sample-stl-1kb.stl), and for .stl objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 16. What metadata headers and part-sizing rules should be used when uploading .svg (SVG) objects to S3 or GCS?
- Set Content-Type to image/svg+xml, include x-amz-meta-sha256 with the 64-character hex digest (ed384263be1c983b… for sample-svg-1kb.svg), and for .svg objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 17. What metadata headers and part-sizing rules should be used when uploading .tar (TAR) objects to S3 or GCS?
- Set Content-Type to application/x-tar, include x-amz-meta-sha256 with the 64-character hex digest (4c6ff6563d9c00f0… for sample-tar-10kb.tar), and for .tar objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 18. What metadata headers and part-sizing rules should be used when uploading .tiff (TIFF) objects to S3 or GCS?
- Set Content-Type to image/tiff, include x-amz-meta-sha256 with the 64-character hex digest (b7bfb311950ba844… for sample-tiff-10kb.tiff), and for .tiff objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 19. What metadata headers and part-sizing rules should be used when uploading .toml (TOML) objects to S3 or GCS?
- Set Content-Type to application/toml, include x-amz-meta-sha256 with the 64-character hex digest (c77a799450a2b039… for sample-toml-1kb.toml), and for .toml objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 20. What metadata headers and part-sizing rules should be used when uploading .tsv (TSV) objects to S3 or GCS?
- Set Content-Type to text/tab-separated-values, include x-amz-meta-sha256 with the 64-character hex digest (1da1f9e2460c95d7… for sample-tsv-1kb.tsv), and for .tsv objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 21. What metadata headers and part-sizing rules should be used when uploading .txt (TXT) objects to S3 or GCS?
- Set Content-Type to text/plain, include x-amz-meta-sha256 with the 64-character hex digest (330c0c29155c03a0… for sample-txt-1kb.txt), and for .txt objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 22. What metadata headers and part-sizing rules should be used when uploading .vtt (WebVTT) objects to S3 or GCS?
- Set Content-Type to text/vtt, include x-amz-meta-sha256 with the 64-character hex digest (58689e501f1d3e9f… for sample-vtt-1kb.vtt), and for .vtt objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 23. What metadata headers and part-sizing rules should be used when uploading .wav (WAV) objects to S3 or GCS?
- Set Content-Type to audio/wav, include x-amz-meta-sha256 with the 64-character hex digest (46a36cb64427f37a… for sample-wav-100kb.wav), and for .wav objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 24. What metadata headers and part-sizing rules should be used when uploading .webm (WebM) objects to S3 or GCS?
- Set Content-Type to video/webm, include x-amz-meta-sha256 with the 64-character hex digest (f30a216fe3ae1225… for sample-webm-100kb.webm), and for .webm objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 25. What metadata headers and part-sizing rules should be used when uploading .webp (WebP) objects to S3 or GCS?
- Set Content-Type to image/webp, include x-amz-meta-sha256 with the 64-character hex digest (feb06afc48077314… for sample-webp-10kb.webp), and for .webp objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 26. What metadata headers and part-sizing rules should be used when uploading .xlsx (XLSX) objects to S3 or GCS?
- Set Content-Type to application/vnd.openxmlformats-officedocument.spreadsheetml.sheet, include x-amz-meta-sha256 with the 64-character hex digest (93a7146f1632eccd… for sample-xlsx-10kb.xlsx), and for .xlsx objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 27. What metadata headers and part-sizing rules should be used when uploading .xml (XML) objects to S3 or GCS?
- Set Content-Type to application/xml, include x-amz-meta-sha256 with the 64-character hex digest (60cac50ebd718050… for sample-xml-1kb.xml), and for .xml objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 28. What metadata headers and part-sizing rules should be used when uploading .yaml (YAML) objects to S3 or GCS?
- Set Content-Type to application/yaml, include x-amz-meta-sha256 with the 64-character hex digest (f3513b2adbffa831… for sample-yaml-1kb.yaml), and for .yaml objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
- 29. What metadata headers and part-sizing rules should be used when uploading .zip (ZIP) objects to S3 or GCS?
- Set Content-Type to application/zip, include x-amz-meta-sha256 with the 64-character hex digest (d93f32774a20ef7e… for sample-zip-1kb.zip), and for .zip objects above 5 MB (up to 100mb), use 8 MB or 16 MB multipart upload chunks.
Part 3: Architecture, implementation and pipeline questions
- 1. Why does an S3 multipart ETag for a 100 MB .avro upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .avro file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 2. Why does an S3 multipart ETag for a 100 MB .bin upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .bin file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 3. Why does an S3 multipart ETag for a 100 MB .bmp upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .bmp file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 4. Why does an S3 multipart ETag for a 100 MB .css upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .css file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 5. Why does an S3 multipart ETag for a 100 MB .csv upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .csv file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 6. Why does an S3 multipart ETag for a 100 MB .docx upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .docx file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 7. Why does an S3 multipart ETag for a 100 MB .eml upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .eml file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 8. Why does an S3 multipart ETag for a 100 MB .epub upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .epub file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 9. Why does an S3 multipart ETag for a 100 MB .flac upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .flac file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 10. Why does an S3 multipart ETag for a 100 MB .geojson upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .geojson file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 11. Why does an S3 multipart ETag for a 100 MB .gif upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .gif file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 12. Why does an S3 multipart ETag for a 100 MB .gltf upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .gltf file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 13. Why does an S3 multipart ETag for a 100 MB .gpx upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .gpx file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 14. Why does an S3 multipart ETag for a 100 MB .gz upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .gz file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 15. Why does an S3 multipart ETag for a 100 MB .html upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .html file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 16. Why does an S3 multipart ETag for a 100 MB .ico upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .ico file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 17. Why does an S3 multipart ETag for a 100 MB .ics upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .ics file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 18. Why does an S3 multipart ETag for a 100 MB .ini upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .ini file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 19. Why does an S3 multipart ETag for a 100 MB .jpg upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .jpg file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 20. Why does an S3 multipart ETag for a 100 MB .js upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .js file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 21. Why does an S3 multipart ETag for a 100 MB .json upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .json file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 22. Why does an S3 multipart ETag for a 100 MB .jsonl upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .jsonl file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
- 23. Why does an S3 multipart ETag for a 100 MB .kml upload contain a hyphen suffix (like '-13') instead of a plain MD5 hash?
- When a 100 MB .kml file is uploaded via S3 CreateMultipartUpload in 8 MB parts, S3 computes the MD5 of the concatenated binary MD5s of each part followed by '-13', so you should store the full SHA-256 checksum in custom object metadata.
Part 4: Verification, edge cases and automation questions
- 1. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .avro uploads?
- Sign both Content-Type (application/avro) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .avro upload that differs by even a single byte.
- 2. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .bin uploads?
- Sign both Content-Type (application/octet-stream) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .bin upload that differs by even a single byte.
- 3. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .bmp uploads?
- Sign both Content-Type (image/bmp) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .bmp upload that differs by even a single byte.
- 4. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .css uploads?
- Sign both Content-Type (text/css) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .css upload that differs by even a single byte.
- 5. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .csv uploads?
- Sign both Content-Type (text/csv) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .csv upload that differs by even a single byte.
- 6. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .docx uploads?
- Sign both Content-Type (application/vnd.openxmlformats-officedocument.wordprocessingml.document) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .docx upload that differs by even a single byte.
- 7. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .eml uploads?
- Sign both Content-Type (message/rfc822) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .eml upload that differs by even a single byte.
- 8. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .epub uploads?
- Sign both Content-Type (application/epub+zip) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .epub upload that differs by even a single byte.
- 9. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .flac uploads?
- Sign both Content-Type (audio/flac) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .flac upload that differs by even a single byte.
- 10. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .geojson uploads?
- Sign both Content-Type (application/geo+json) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .geojson upload that differs by even a single byte.
- 11. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .gif uploads?
- Sign both Content-Type (image/gif) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .gif upload that differs by even a single byte.
- 12. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .gltf uploads?
- Sign both Content-Type (model/gltf+json) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .gltf upload that differs by even a single byte.
- 13. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .gpx uploads?
- Sign both Content-Type (application/gpx+xml) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .gpx upload that differs by even a single byte.
- 14. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .gz uploads?
- Sign both Content-Type (application/gzip) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .gz upload that differs by even a single byte.
- 15. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .html uploads?
- Sign both Content-Type (text/html) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .html upload that differs by even a single byte.
- 16. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .ico uploads?
- Sign both Content-Type (image/vnd.microsoft.icon) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .ico upload that differs by even a single byte.
- 17. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .ics uploads?
- Sign both Content-Type (text/calendar) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .ics upload that differs by even a single byte.
- 18. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .ini uploads?
- Sign both Content-Type (text/plain) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .ini upload that differs by even a single byte.
- 19. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .jpg uploads?
- Sign both Content-Type (image/jpeg) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .jpg upload that differs by even a single byte.
- 20. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .js uploads?
- Sign both Content-Type (text/javascript, per RFC 9239) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .js upload that differs by even a single byte.
- 21. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .json uploads?
- Sign both Content-Type (application/json) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .json upload that differs by even a single byte.
- 22. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .jsonl uploads?
- Sign both Content-Type (application/jsonl) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .jsonl upload that differs by even a single byte.
- 23. How do presigned PUT URLs enforce exact Content-Length and Content-Type on client-direct .kml uploads?
- Sign both Content-Type (application/vnd.google-earth.kml+xml) and Content-Length in the S3 SigV4 canonical request so the storage bucket rejects any .kml upload that differs by even a single byte.
Explore all 40 topic-based technical format references
Browse the complete engineering reference library on Testing guides or Frequently asked questions.