A regional evidence unit must upload multi-gigabyte case media from distant field offices into Amazon S3 when WAN latency is high. Which approach best improves large remote ingest performance?
Select an answer to reveal the explanation.
Short Explanation
Big remote uploads hate chatty single-stream transfers over high latency—think mailing a library one page at a time. Multipart upload plus S3 Transfer Acceleration chops the work and uses edge-optimized paths so distant offices finish sooner. Turning multipart off, waiting on monthly disks, or funnelling everything through one NAT just slows the pipeline.
Full Explanation
For large object ingest over high-latency networks, multipart upload improves reliability and parallelism, while S3 Transfer Acceleration routes traffic through CloudFront edge locations to optimize long-distance transfers to a destination bucket. That combination is the associate-level pattern for fast remote evidence ingest. Disabling multipart, offline media shipping as the primary design, or concentrating traffic on a single NAT path does not optimize WAN upload performance.