# Policy Inheritance

Policy inheritance is the application of policies from a parent scope to its descendants according to defined evaluation and override rules.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/policy-inheritance

> Cloud platforms use policy inheritance to apply common governance requirements across organizational hierarchies without configuring every account, project, or resource separately. The effective result depends on the policy type: some policies impose permission ceilings, while others merge configuration settings or allow controlled overrides.

Practice exams covering Policy Inheritance: [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 6 key aspects of Policy Inheritance

Effective inherited policy depends on the hierarchy, policy semantics, authorization boundaries, override rules, and supported enforcement scope.

1. **Hierarchical scope**: Policies flow from parent scopes to applicable descendants. Account placement and organizational-unit moves are therefore security-relevant changes, not merely administrative housekeeping.
2. **Policy-specific evaluation**: Permission boundaries, configuration settings, and management preferences do not share one inheritance algorithm. Determine whether the policy uses intersection, merging, replacement, or controlled overrides before evaluating its effect.
3. **Restrictions are not grants**: SCPs and RCPs constrain authorization but do not independently authorize requests. Required permissions must still come from the applicable identity-based or resource-based authorization mechanisms.
4. **Explicit override rules**: A child policy cannot override an inherited authorization deny. Management policy types can permit or prohibit child changes through their own inheritance controls.
5. **Identity and resource boundaries**: Identity-oriented controls restrict what principals can do, while resource-oriented controls restrict access to protected resources. Using both can address requests that cross account or organizational boundaries.
6. **Controlled rollout and verification**: Test inherited controls against representative workloads before broad deployment. Review ancestor policies, direct attachments, scope exceptions, and recent hierarchy changes when troubleshooting unexpected behavior.

## Cloud services for Policy Inheritance

AWS Organizations supplies the hierarchy and policy attachments for centralized AWS governance, while AWS Control Tower uses that foundation to establish and operate a governed multi-account environment. Their roles complement each other: organization policies define applicable boundaries or configuration requirements, and Control Tower coordinates controls and account governance. Azure Policy and Google Cloud Organization Policy provide comparable hierarchical governance within their respective platforms, not a shared cross-cloud enforcement layer. Across all of them, engineers must evaluate ancestor policies, local assignments, exclusions, and policy-specific conflict rules. Neither organizational placement nor a permissive local policy alone proves that an operation is allowed.

- **[AWS Organizations](https://blowstack.com/tools/cloud-services-hub/aws-organizations)**: Provides the root, organizational-unit, and account hierarchy through which organization policies are inherited. SCPs, RCPs, AI services opt-out policies, and declarative policies use this hierarchy but have different enforcement and inheritance semantics.
- **[AWS Control Tower](https://blowstack.com/tools/cloud-services-hub/aws-control-tower)**: Builds a governed multi-account environment using AWS Organizations and other AWS services. Its preventive controls can use inherited organization policies, while detective and proactive controls use different mechanisms and must not be treated as equivalent inherited permission boundaries.

## Policy Inheritance exam questions

Real practice exam questions on Policy Inheritance, with the correct answer and its explanation.

### Question 1 (SOA-C03)

**Question:**

A company uses AWS Organizations with all features enabled. A Workloads organizational unit (OU) contains two child OUs: Standard and Maintenance. FullAWSAccess service control policies (SCPs) are attached at the organization root, every OU, and every member account. An additional SCP attached to Workloads explicitly denies ec2:StopInstances.

A CloudOps engineer moves a member account from Standard to Maintenance. An IAM role in the account allows ec2:StopInstances, but attempts to stop instances are still denied. No other policies restrict the operation.

The company requires roles with appropriate IAM permissions in Maintenance accounts to be able to stop instances. Stopping instances must remain prohibited in all current and future Standard accounts, without configuring SCPs on individual accounts.

Which change meets these requirements?

**Correct answer:** Detach the deny SCP from Workloads and attach it to Standard, leaving the FullAWSAccess attachments unchanged.

**Explanation:** Maintenance accounts will no longer inherit the explicit deny, so the role's IAM permissions can authorize the operation. Attaching the deny to Standard enforces the restriction for its existing accounts and accounts added there later without account-level SCP configuration.

### Question 2 (SAP-C03)

**Question:**

A financial services company uses AWS Organizations with all features enabled. FullAWSAccess is the only SCP attached to the organization root, each OU, and each member account. Workload administrators have IAM roles with AdministratorAccess and can create additional IAM roles and policies.

The company must restrict IAM users and roles in every current and future member account to a centrally approved set of AWS services. Newly launched AWS services must remain unavailable until the security team explicitly approves them. The restriction must apply even to accounts created directly under the root or moved between OUs. Administrators must retain their existing IAM-authorized access to approved services. Only the security team can modify SCPs.

Which solution meets these requirements with the LEAST ongoing policy administration?

**Correct answer:** Replace FullAWSAccess at the root with an SCP that allows all actions for only the approved services. Retain FullAWSAccess on the OUs and member accounts, and retain the existing IAM policies.

**Explanation:** The root-level allowlist constrains IAM principals in all member accounts, including accounts created directly under the root or moved between OUs. Services absent from the allowlist, including newly launched services, are implicitly denied by the SCP ceiling. Descendant FullAWSAccess policies cannot expand that ceiling, but they preserve the required SCP allows at lower levels. Existing IAM policies still grant the actual permissions for approved services.

### Question 3 (SAA-C03)

**Question:**

A company uses AWS Organizations with all features enabled. A workload member account is moved from the Development organizational unit (OU) to the Production OU. Both OUs are direct children of the organization root.

The SCP configuration is as follows:
• The root, both OUs, and the workload account each have FullAWSAccess attached.
• Development has an additional SCP that explicitly denies ec2:StopInstances.
• Production has an additional SCP that explicitly denies ec2:TerminateInstances.
• The workload account has a directly attached SCP that explicitly denies ec2:DeleteSnapshot.

After the move has propagated, an operations engineer uses an existing IAM role with AdministratorAccess in the workload account to run a maintenance procedure. The procedure stops an EC2 instance, terminates another EC2 instance, and deletes an account-owned EBS snapshot. All resources are otherwise eligible for these operations, and no other policies restrict access.

Which result should a solutions architect expect?

**Correct answer:** Stopping the instance succeeds. Terminating the other instance and deleting the snapshot are denied.

**Explanation:** The account no longer inherits the Development OU's deny on stopping instances. It now inherits Production's deny on terminating instances. The SCP attached directly to the account remains attached after the move, so snapshot deletion is still denied. AdministratorAccess cannot override either explicit deny.

### Question 4 (SCS-C03)

**Question:**

A company uses AWS Organizations with all features enabled. Its Research OU contains member accounts whose administrators manage Amazon EBS snapshots. Some existing snapshots are publicly shared, and others are privately shared with approved AWS accounts.

The security team must centrally prevent public access to existing and future snapshots in every AWS Region, while preserving private sharing with specified accounts. Account administrators must not be able to weaken the protection, and the protection must automatically apply to accounts subsequently added to the Research OU. The solution must not require changes to individual snapshots' sharing permissions.

Which solution meets these requirements?

**Correct answer:** Enable declarative policies for Amazon EC2 in AWS Organizations. Attach a policy to the Research OU that enforces EBS Snapshot Block Public Access in block-all-sharing mode, and disallow child policies from changing that setting.

**Explanation:** An EC2 declarative policy can centrally enforce the account-level EBS Snapshot Block Public Access setting across Regions. Block-all-sharing mode prevents public access to both existing and future publicly shared snapshots without changing individual snapshot permissions. Private sharing with specified accounts remains available. OU inheritance covers subsequently added accounts, and preventing child overrides preserves the enforced setting.

### Question 5 (DOP-C02)

**Question:**

A company uses AWS Organizations with all features enabled. An Operations OU contains a nested Production OU. All production workload accounts belong to the Production OU. FullAWSAccess SCPs are attached to the organization root, the Production OU, and each workload account. The only SCP attached to the Operations OU is an allow-list policy that permits approved API actions but omits ec2:ModifyInstanceMetadataOptions. No applicable SCP contains an explicit Deny.

A security automation role in each workload account must configure EC2 instances to require IMDSv2 across three AWS Regions. The roles already have identity-based permissions for ec2:ModifyInstanceMetadataOptions, and no other authorization controls block the action. Test executions fail with an authorization error.

A DevOps engineer must enable this automation for all existing and future accounts under the Operations OU while preserving all currently approved actions and keeping unapproved actions outside the SCP permission ceiling.

Which change meets these requirements?

**Correct answer:** Attach an additional SCP to the Operations OU that allows ec2:ModifyInstanceMetadataOptions on all resources. Retain the existing allow-list SCP and all other SCP attachments.

**Explanation:** Allows from SCPs attached at the same level combine. The additional policy supplies the missing allow at the Operations OU without removing its existing approved actions or allowing unrelated actions. The root, Production OU, and account levels already allow the action. Applicable descendants, including future accounts, inherit the resulting permission ceiling.

## Practice Policy Inheritance in a full exam

Questions on Policy Inheritance in each practice exam, with every answer option and an explanation for each:

- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 9 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 8 questions
- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 7 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 6 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 5 questions

## What is Policy Inheritance

Policy inheritance connects governance rules to an organizational hierarchy. A policy attached to a parent scope can affect all applicable descendants, including descendants created or moved there later. Typical scopes include an organization, organizational unit, folder, account, subscription, or project. This lets a platform team establish a common baseline while delegating day-to-day administration to workload teams.

Inheritance does not have one universal evaluation algorithm. An authorization policy might restrict permissions, a configuration policy might combine settings, and another policy might allow a child to replace an inherited value. Engineers must identify the policy type, its attachment scope, supported targets, conflict rules, and exceptions before predicting the effective outcome. A policy attached directly to a child is not automatically more authoritative than an inherited policy.

In AWS Organizations, policies can be attached to the organization root, organizational units, or accounts. An account inherits applicable policies along its path through the hierarchy. Organization policy types must be enabled before use, and authorization policies such as service control policies require an organization operating with all features enabled. Organizational units are governance boundaries, not IAM identities, and moving an account between them can change its effective controls without changing its IAM policies.

Service control policies, or SCPs, establish the maximum permissions available to principals in member accounts. They do not grant permissions. For an action to pass SCP evaluation, it must be allowed at every level from the root through the account, and an applicable explicit deny at any level blocks it. Allows from multiple SCPs attached at the same level combine, but a child-level allow cannot overcome a missing parent-level allow or an inherited explicit deny. For example, an inherited deny on disabling audit logging still blocks an account administrator whose IAM policy allows that action. SCPs do not restrict principals in the management account and do not affect service-linked roles.

Resource control policies, or RCPs, apply a complementary boundary to resources in member accounts for supported services. They constrain access to those resources, including access by external principals, rather than defining the permissions of the requesting account's identities. An inherited RCP can therefore restrict external access to supported storage resources even when a resource policy permits it. RCPs do not grant access, do not cover every resource type, and do not apply to resources in the management account.

Management policies use different inheritance semantics. AI services opt-out policies control whether supported AI services may use specified customer content for service improvement; they do not deny permission to invoke those services. Parent and child settings combine into an effective policy, with inheritance operators controlling which changes descendants may make. An organization-wide opt-out should therefore include appropriate restrictions on child overrides when exceptions are not intended.

Declarative policies specify supported service configurations rather than evaluating individual API requests as permission boundaries. For example, an organization can enforce supported EC2 public-access settings through an inherited configuration policy. These policies also use policy-specific inheritance rules and can restrict child modifications. An SCP that denies a configuration-changing API and a declarative policy that establishes the configuration are different mechanisms, even when they support the same governance objective.

The main benefit is consistent control with less duplicated configuration. The trade-off is a larger potential impact from mistakes: a root-level change can affect many workloads, and an account move can introduce unexpected restrictions. Test changes in a representative organizational unit, inspect effective policies where supported, allow for propagation, and validate both permitted and prohibited operations. Place mandatory controls high enough to cover their intended population, place optional restrictions lower down, and design exceptions explicitly rather than assuming a local administrator can override inherited rules.

## Learn Policy Inheritance in lessons

6 short lessons on Policy Inheritance in 5 certification courses.

- SOA-C03: Policy Inheritance: SCPs across the organization hierarchy (Premium), https://app.blowstack.com/lessons/policy-inheritance-scps-across-the-organization-hierarchy-soa-c03
- SAP-C03: Policy Inheritance: SCP and RCP boundaries across account hierarchies (Premium), https://app.blowstack.com/lessons/policy-inheritance-scp-and-rcp-boundaries-across-account-hierarchies-sap-c03
- SAA-C03: Policy Inheritance: SCPs across the account hierarchy (Premium), https://app.blowstack.com/lessons/policy-inheritance-scps-across-the-account-hierarchy-saa-c03
- SCS-C03: Policy Inheritance: configuration merging and controlled overrides (Premium), https://app.blowstack.com/lessons/policy-inheritance-configuration-merging-and-controlled-overrides-scs-c03
- DOP-C02: Policy Inheritance: SCP boundaries across organizational hierarchies (Premium), https://app.blowstack.com/lessons/policy-inheritance-scp-boundaries-across-organizational-hierarchies-dop-c02
- SCS-C03: Policy Inheritance: permission ceilings across the hierarchy (Premium), https://app.blowstack.com/lessons/policy-inheritance-permission-ceilings-across-the-hierarchy-scs-c03
