Exam AWS Certified Solutions Architect - Associate SAA-C02 topic 1 question 535 discussion

fter you set up cross-Region replication (CRR) or same-Region replication (SRR) on the source bucket, Amazon S3 automatically and asynchronously replicates new objects from the source bucket to the destination bucket. You can choose to filter which objects are replicated using a prefix or tag. For more information on configuring replication and specifying a filter, see Replication configuration overview. After replication is configured, only new objects are replicated to the destination bucket. Existing objects aren't replicated to the destination bucket. For more information, see Replicating existing objects. https://aws.amazon.com/premiumsupport/knowledge-center/s3-large-transfer-between-buckets/

B To copy objects from one S3 bucket to another, follow these steps: 1. Create a new S3 bucket. 2. Install and configure the AWS Command Line Interface (AWS CLI). 3. Copy the objects between the S3 buckets

D is the answer

B is the correct answer. Look at the second bullet point in the documentation. https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-batch-replication-batch.html

D 100% https://aws.amazon.com/blogs/storage/replicating-existing-objects-between-s3-buckets/

https://aws.amazon.com/premiumsupport/knowledge-center/s3-large-transfer-between-buckets/ I want to transfer a large amount of data (1 TB or more) from one Amazon Simple Storage Service (Amazon S3) bucket to another bucket. How can I do that? Run parallel uploads using the AWS Command Line Interface (AWS CLI) Use an AWS SDK Use cross-Region replication or same-Region replication Use Amazon S3 batch operations Use S3DistCp with Amazon EMR Use AWS DataSync

CRR will work ONLY on new objects AFTER it has been enabled. B is not possible to use Console. C also not possible

I'd go for C although the Transfer Accelerations doesn't show up in AWS documentation for this use case. https://aws.amazon.com/premiumsupport/knowledge-center/s3-large-transfer-between-buckets/ A - Doesn't work here, data is already in AWS B - Using the AWS Console is not an option for this. C - CLI would work and can be turned (but there's no mention to Transfer Acceleration in the AWS docs) D - It won't replicate existing data (maybe it could be done with AWS support but that's another step not included in the answer).

As of 2/10/22 existing s3 objects can be replicated using S3 batch replication https://aws.amazon.com/blogs/storage/replicating-existing-objects-between-s3-buckets/ UPDATE (2/10/2022): Amazon S3 Batch Replication launched on 2/8/2022, allowing you to replicate existing S3 objects and synchronize your S3 buckets. See the S3 User Guide for additional details.

The answer is D. https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication-what-is-isnot-replicated.html#replication-what-is-not-replicated “What isn't replicated with replication configurations? - Objects in the source bucket that have already been replicated to a different destination. For example, if you change the destination bucket in an existing replication configuration, Amazon S3 won't replicate the objects again.To replicate previously replicated objects, use Batch Replication. Learn more about configuring Batch Replication at Replicate existing objects” In this question, they never mentioned that the S3 objects are already replicated, these are brand new copies.

I saw another version of the answer C. Use the AWS S3 sync command to copy data from the source bucket to the destination bucket. My opinion C is the answer. Cross-Region-Replication doesn't copy existing data in S3. For existing data, another option is S3 Batch Replication

A. Snowball Egde : Storage Optimized (max 80TB) 1 peta = 80TB * 13 edges maybe. B. S3 console copy (max 5GB) : You can create a copy of your object up to 5 GB in a single atomic operation. However, to copy an object that is greater than 5 GB, you must use the multipart upload API. Using the copy operation, you can: (1)Create additional copies of objects (2)Rename objects by copying them and deleting the original ones (3)Move objects across Amazon S3 locations (for example, us-west-1 and Europe) (4)Change object metadata in case of over 5GB, multipart upload API is required. C. Amazon S3 Transfer Acceleration is for between client and an S3 bucket.It transfers files over long distances between your client and an S3 bucket. D. Cross-Region Replication is not for old objects.

B.Why use Transfer Acceleration? You might want to use Transfer Acceleration on a bucket for various reasons: Your customers upload to a centralized bucket from all over the world. You transfer gigabytes to terabytes of data on a regular basis across continents. You can't use all of your available bandwidth over the internet when uploading to Amazon S3. D.Objects that existed before you set up replication aren't replicated automatically. In other words, Amazon S3 doesn't replicate objects retroactively. To replicate objects that were created before your replication configuration, use S3 Batch Replication. Learn more about configuring Batch Replication at Replicate existing objects.

There's no need to use a snowball device. The data is already in one S3 region. S3 console cannot move the data all at once; however, you could do this from the CLI. S3 Transfer Acceleration is about moving files quickly to the customer. The best option is S3 Cross-Region Replication. When you set up the replication rule, you can opt to run a batch operation to move over pre-existing objects from the source bucket (new feature).

cross-Region replication (CRR) only works on new objects. It will not move existing objects.

IMO: D is correct (existing objects also possible)/ others don't replicate

"You may optionally enable existing object replication for your account. In order to do so you must contact AWS Support. To prevent your request from being delayed, title your AWS Support case "Replication for Existing Objects" and be sure to include the following information:" https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication-what-is-isnot-replicated.html#existing-object-replication