Question
A company uses AWS Organizations to manage multiple AWS accounts for different departments. The management account has an Amazon S3 bucket that contains project reports. The company wants to limit access to this S3 bucket to only users of accounts within the organization in AWS Organizations.
Which solution meets these requirements with the LEAST amount of operational overhead?
- A. Add the aws:PrincipalOrgID global condition key with a reference to the organization ID to the S3 bucket policy. Correct
- B. Create an organizational unit (OU) for each department. Add the aws:PrincipalOrgPaths global condition key to the S3 bucket policy.
- C. Use AWS CloudTrail to monitor the CreateAccount, InviteAccountToOrganization, LeaveOrganization, and RemoveAccountFromOrganization events. Update the S3 bucket policy accordingly.
- D. Tag each user that needs access to the S3 bucket. Add the aws:PrincipalTag global condition key to the S3 bucket policy.
Explanation
Option A is correct because using the aws:PrincipalOrgID global condition key in the S3 bucket policy allows you to restrict access to users within a specific AWS Organizations organization by referencing the organization ID. This approach requires minimal operational overhead as it does not involve creating additional OUs, monitoring events with CloudTrail, or tagging individual users.
