Which solution will meet these requirements?
Create an Amazon EventBridge rule that listens to S3 event notifications for failed replication events. Create an AWS Lambda function that downloads the failed replication object and then runs a PutObject command for the object to the destination bucket. Configure the EventBridge rule to invoke the Lambda function to handle the object that failed to replicate.
Create an Amazon Simple Queue Service (Amazon SQS) queue. Configure S3 event notifications to send failed replication notifications to the SQS queue. Create an AWS Lambda function that downloads the failed replication object and then runs a PutObject command for the object to the destination bucket. Configure the Lambda function to poll the queue for notifications to process.
Create an Amazon EventBridge rule that listens to S3 event notifications for failed replications. Create an AWS Lambda function that downloads the failed replication object and then runs a PutObject command for the object to the destination bucket.
Create an AWS Lambda function that will use S3 batch operations to retry the replication on the existing object for a failed replication. Configure S3 event notifications to send failed replication notifications to the Lambda function.
Explanations:
EventBridge cannot directly trigger replication retries. Lambda would need to manually handle retries which is not the most efficient solution.
SQS can be used for event handling, but S3 event notifications are not designed to handle replication retries. This solution would require more custom management.
Similar to Option A, but without the use of SQS. EventBridge alone cannot trigger retries for replication failures; it would require additional handling outside the native functionality.
Lambda can process failed replication notifications and use S3 batch operations to retry replication, which is the intended and most efficient approach to retry replication.