A Solutions Architect wants to grant a development team in a member account the ability to manage Amazon S3 buckets. The architect attaches a Service Control Policy (SCP) to the Organizational Unit (OU) containing the member account, which explicitly allows all S3 actions. However, the developers in the member account still receive access denied errors when attempting to create a bucket. Which of the following explains this behavior?
- ASCPs automatically grant S3 permissions to all IAM entities in the member account, but the policy failed to apply because the member account's administrator explicitly blocked the inheritance of the policy.
- SCPs act as permission guardrails that define the maximum allowed permissions but do not grant access directly. The developers still require a local IAM policy in their account that explicitly grants S3 permissions.Answer
- CThe S3 actions are allowed by the SCP, but the developers cannot access S3 until the S3 service is shared with the member account using a resource share in AWS Resource Access Manager.
- DThe S3 permissions are allowed by the SCP, but the actions fail because S3 requires a Customer Managed Key (CMK) policy update to allow cross-account bucket access.
Answer
The correct answer states that SCPs act as permission guardrails that define the maximum allowed permissions but do not grant access directly, and that the developers still require a local IAM policy in their account that explicitly grants S3 permissions.
The correct answer states that SCPs act as permission guardrails and do not grant access directly, meaning the developers still require a local IAM policy in their account. This reflects the core concept that AWS authorization requires an explicit allow in both the SCP and the local IAM policy.
Step-by-Step Solution
Key Concept
Service Control Policies (SCPs) act as permission boundaries and do not grant permissions directly. Local IAM policies must be configured to grant access.
Estimated Time:1m 0s