QuestionQ59

VerifiedDesign Solutions for Organizational Complexity

A company uses AWS Organizations with one OU, named Production, to manage multiple accounts. Every account belongs to the Production OU. Administrators use deny-list SCPs at the organization root to control access to restricted services.

The company recently acquired a new business unit and invited that unit’s existing AWS account into the organization. After onboarding, the new business unit’s administrators found that they could not update existing AWS Config rules to comply with company policies.

Which option will enable administrators to make changes while continuing to enforce the current policies without adding long-term maintenance?

Explanation

An SCP attached to the organization root applies to every member account and OU below it, and an explicit Deny cannot be overridden by an Allow at a lower level. Moving the deny-list SCP from the root to the Production OU keeps the existing restrictions in force for all production accounts while an account in a separate Onboarding OU can perform the required AWS Config updates. The account can be moved to Production after onboarding, restoring the same guardrails without a permanent exception.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!