What is the MOST efficient way to upload the device data to Amazon S3 while managing storage costs?
Upload device data using a multipart upload. Use the AWS CLI to list incomplete parts to address the failed S3 uploads. Enable the lifecycle policy for the incomplete multipart uploads on the S3 bucket to delete the old uploads and prevent new failed uploads from accumulating.
Upload device data using S3 Transfer Acceleration. Use the AWS Management Console to address the failed S3 uploads. Use the Multi-Object Delete operation nightly to delete the old uploads.
Upload device data using a multipart upload. Use the AWS Management Console to list incomplete parts to address the failed S3 uploads. Configure a lifecycle policy to archive continuously to Amazon S3 Glacier.
Upload device data using S3 Transfer Acceleration. Use the AWS Management Console to list incomplete parts to address the failed S3 uploads. Enable the lifecycle policy for the incomplete multipart uploads on the S3 bucket to delete the old uploads and prevent new failed uploads from accumulating.
Explanations:
Using multipart upload is suitable for large files, as it splits uploads into smaller parts, reducing the chance of failure. AWS CLI can list incomplete parts to handle failures. Enabling a lifecycle policy for incomplete uploads prevents storage accumulation, effectively managing costs associated with failed and incomplete uploads.
S3 Transfer Acceleration increases upload speed but does not address the issue of managing failed uploads and does not reduce storage costs related to incomplete uploads. Using Multi-Object Delete does not specifically target failed multipart uploads, so storage costs due to incomplete uploads may still persist.
Although multipart upload is correct for large files, archiving to S3 Glacier increases retrieval costs and is not a viable method for actively used data. Using the AWS Management Console to list incomplete parts is inefficient compared to using the AWS CLI. This approach does not effectively manage storage costs associated with incomplete uploads.
S3 Transfer Acceleration is not necessary for the solution, as it focuses on upload speed rather than addressing failed uploads or storage management. The AWS Management Console is not efficient for handling incomplete parts. Although the lifecycle policy for incomplete uploads is correct, the overall approach does not optimize storage costs well.
I measure that the answer is:
Upload device data using a multipart upload. Use the AWS CLI to list incomplete parts to address the failed S3 uploads. Enable the lifecycle policy for the incomplete multipart uploads on the S3 bucket to delete the old uploads and prevent new failed uploads from accumulating.