A SysOps Administrator is setting up Amazon S3 replication to copy data between two buckets. After configuring the replication rules and applying the configuration, the administrator notices that objects uploaded to the source bucket are not appearing in the destination bucket, and the replication status shows as failed.
Which configuration errors could be causing this replication failure? (Select TWO.)
- The IAM trust policy of the replication role does not list the s3.amazonaws.com service principal as a trusted entity.Answer
- S3 versioning is enabled on the source bucket, but it has not been enabled on the destination bucket.Answer
- CS3 versioning is suspended on the destination bucket to optimize storage costs, as only the source bucket requires active versioning.
- DThe replication role's permissions policy contains the iam:PassRole action on the destination bucket resource rather than S3 API permissions.
- EThe destination bucket has a lifecycle rule configured to transition objects back to S3 Standard from S3 Standard-IA within 15 days of replication.
Answer
The correct configurations are to ensure the IAM trust policy of the replication role trusts the Amazon S3 service principal, and S3 versioning is enabled on both the source and destination buckets.
The replication configuration requires both source and destination S3 buckets to have versioning enabled. In addition, the IAM role used by S3 for replication must have a trust policy allowing the Amazon S3 service principal (s3.amazonaws.com) to assume the role via sts:AssumeRole.
Step-by-Step Solution
Key Concept
Amazon S3 replication requires versioning enabled on both buckets and a correct IAM trust policy allowing S3 to assume the replication role.