Restrict Use of Non-Approved AWS Regions
Specification & Description
Use Service Control Policies (SCPs) and Account Management region controls to deny access to AWS regions that are not approved for your landing zone.
Technical Specifications
Limiting active AWS regions reduces your attack surface, keeps data residency inside approved jurisdictions, and prevents workloads from spinning up in unmonitored regions where security tooling is not deployed. In AWS Organizations, an SCP attached at the Root or OU level denies API requests when aws:RequestedRegion is outside your approved list, while a NotAction block exempts global and us-east-1 control-plane services such as IAM, STS, Organizations, CloudFront, Route 53, Billing, Budgets, Cost Explorer, Support, Trusted Advisor, WAF, Shield, Account Management, and Global Accelerator. Pair the SCP with aws account disable-region for unused opt-in regions. SCPs never apply to the Management account, so restrict Management account operators separately through IAM policies.
Security Rationale
Unused AWS regions become blind spots for CloudTrail, AWS Config, GuardDuty, and Security Hub if regional aggregators or StackSets miss them. Enforcing an allowlist of regions keeps data sovereignty intact and stops unauthorized provisioning before resources exist.
Business & Security Impact
Provisioning resources in unapproved regions violates data residency rules, leaves workloads unmonitored, and creates unexpected billing exposure. An incomplete NotAction exemption list in a region-deny SCP will break console sign-ins, STS role assumptions, billing dashboards, and Control Tower operations in member accounts.
Policy Exceptions (1)
AWS Control Tower automation or break-glass roles that perform regional bootstrapping across accounts may require an ArnNotLike condition on aws:PrincipalArn when provisioning in newly approved regions before SCP updates roll out.
Operational & Implementation Notes
Review the NotAction list quarterly against AWS Control Tower AWS-GR_REGION_DENY updates, as AWS periodically launches new global services or regionalizes existing control-plane endpoints.
Related Controls & Guardrails (2)
Compliance Framework Mappings (4)
Regulatory baselines and industry standards mapped to this control specification.
| Framework / Standard | Mapped Requirements & Controls | Controls |
|---|---|---|
NIST 800-53 Rev 5NIST 800-53 | AC-3AC-4CM-7SC-7 | 4 |
ISO 27001:2022ISO 27001 | A.5.31A.8.9 | 2 |
PCI DSS v4.0PCI DSS | 2.2.17.2.1 | 2 |
SOC 2SOC 2 | CC6.1CC6.6 | 2 |
* Compliance framework mappings are provided for informational architectural reference. Always verify control alignment against your organization's formal audit requirements.
Automated Detection & Rule Logic
Detection Engine: aws-api • Automated: Yes
Verify SERVICE_CONTROL_POLICY is enabled on the organization root, inspect custom SCPs attached to Root or OUs for aws:RequestedRegion Deny conditions and complete NotAction exemptions, check policy attachment targets, and list enabled opt-in regions via Account Management. Required IAM permissions: organizations:ListRoots, organizations:ListPolicies, organizations:ListPoliciesForTarget, organizations:DescribePolicy, organizations:ListTargetsForPolicy, and account:ListRegions.
Remediation Guide & Automation
Enable SERVICE_CONTROL_POLICY on the organization root, deploy a region-deny SCP with full global control-plane exemptions in NotAction (or enable AWS Control Tower AWS-GR_REGION_DENY / CT.MULTISERVICE.PV.1), test in a non-production OU, attach to target OUs or Root, and disable unused opt-in regions. Required IAM permissions: organizations:ListRoots, organizations:EnablePolicyType, organizations:CreatePolicy, organizations:AttachPolicy, and account:DisableRegion.
Step-by-Step Instructions
- Confirm the approved region list based on data residency, latency, and service availability requirements.
- Verify the SCP NotAction list includes all required global control-plane services (IAM, STS, Organizations, CloudFront, Route 53, Billing, Budgets, Cost Explorer, Support, WAF, Shield, Account, Global Accelerator).
- Create the region-deny SCP in the Management account and attach it to a sandbox or non-production OU first.
- Validate CI/CD pipelines, IAM Identity Center sessions, and Control Tower baselines, then attach the SCP to production OUs or Root.
- Disable unused opt-in regions per account using AWS Account Management.