Cross-Account Access with Service Control Policies
What you'll learn: How AWS Service Control Policies (SCPs) act as organization-wide guardrails that can override even cross-account access permissions.
The SCP Override Layer
You've learned about cross-account access through AssumeRole, trust policies, and resource-based policies. But there's a higher authority: Service Control Policies (SCPs) applied at the AWS Organizations level. SCPs create permission boundaries that apply to all accounts in your organization, including cross-account scenarios.
Think of SCPs as the organization's master security policy. Even if Account A grants Account B full AssumeRole access through a trust policy, an SCP in Account B can still block specific actions. SCPs act as a maximum permission filter—they don't grant access, but they can deny it.
How SCPs Affect Cross-Account Access
When a principal in Account A assumes a role in Account B, the effective permissions are the intersection of:
- The identity-based policies attached to the role in Account B
- Any permission boundaries on that role
- The SCPs applied to Account B's organizational unit or account
If an SCP in Account B denies an action (like s3:DeleteBucket), no cross-account principal can perform it—regardless of what the role's policies allow.
Organization-Wide Access Controls
SCPs enable centralized security governance. You can:
- Deny access to sensitive services (e.g.,
"Deny": ["iam:DeleteRole"]) across all accounts - Prevent data exfiltration by blocking certain regions
- Enforce encryption requirements organization-wide
- Block privilege escalation paths even when cross-account roles exist
The policy evaluation happens at the account level, so cross-account access requests are subject to the target account's SCPs.
Key Takeaway: Service Control Policies create organization-wide permission guardrails that override all other policies, including cross-account trust relationships—acting as the final authority on what actions are permitted in member accounts.