Upload a backup that is several dozen gigabytes to S3.
Use parallel transfer and avoid restarting the entire upload after a network failure.
Which method is most appropriate?
Use S3 multipart upload to transfer parts in parallel and retry only the failed parts.
Detailed explanation
An archive storage class addresses retention and retrieval, not multipart transfer.
An archive storage class addresses retention and retrieval, not multipart transfer.
Multipart upload splits the object into parts, supports parallel transfer, and allows failed parts to be retried.
Multipart upload splits the object into parts, supports parallel transfer, and allows failed parts to be retried.
Route 53 is a DNS service and not a large-object storage system.
Route 53 is a DNS service and not a large-object storage system.
A failure requires the whole large request to be sent again.
A failure requires the whole large request to be sent again.
Check official documentation
Compare the following points with the official documentation.
Amazon S3 multipart uploadの公式説明を確認する。
What to confirm
大容量ファイルの転送方式をマルチパートアップロードへ対応付けられる。
Key points
- S3 multipart upload
- Parallel transfer
- Partial retry
Notes
- Environment: AWS公式S3ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Transfer resilience
Multipart upload limits the impact of a connection failure on a large transfer.
Storage class versus transfer
Glacier and other classes affect storage and retrieval, not how the upload is split.