A digitization team uploads many large scanned permit packets to Amazon S3 daily. Leadership asks how to reduce PUT request overhead and stored bytes without changing durability goals. Which upload strategy best helps?
Select an answer to reveal the explanation.
Short Explanation
Big scanned packets love two thrifty habits: squeeze the air out (compress) and use multipart so large files transfer efficiently. Tiny one-byte PUT storms, fragile single-shot multi-GB uploads, and five-Region duplicates before compression burn money for no durability win.
Full Explanation
Cost-aware ingest reduces both request counts and stored bytes: compression (when suitable for the content) lowers storage footprint, and multipart upload improves reliability and efficiency for large objects. Extremely small object patterns inflate PUT costs; avoiding multipart for huge files increases failure risk; storing many pre-compression replicas multiplies spend. Efficient multipart plus compression is the upload strategy that lowers cost while preserving durability targets.