A SysOps Administrator is writing an AWS Lambda function in AWS Account A to put objects in an Amazon S3 bucket in AWS Account B. The Lambda function is able to successfully write new objects to the S3 bucket, but IAM users in Account B are unable to delete objects written to the bucket by Account A. Which step will fix this issue?
A) Add s3:DeleteObject permission to the IAM execution role of the AWS Lambda function in Account A. Add s3:DeleteObject permission to the IAM execution role of the AWS Lambda function in Account A.
B) Change the bucket policy of the S3 bucket in Account B to allow s3:DeleteObject permission for Account A. Change the bucket policy of the S3 bucket in Account B to allow permission for Account A.
C) Disable server-side encryption for objects written to the S3 bucket by the Lambda function.
D) Modify the Lambda function to call the S3:PutObjectAcl API operation to specify bucket owner, full control. Modify the Lambda function to call the S3:PutObjectAcl API operation to specify bucket owner, full control.

Question

Quizplus · Accepted Answer

The issue is that objects written by Account A are owned by Account A, so Account B users can't delete them. By using S3:PutObjectAcl to give the bucket owner full control, Account B users will be able to manage the objects.

A SysOps Administrator Is Writing an AWS Lambda Function in AWS