34 of 50 in All Controls
aws

Restrict Use of Non-Approved AWS Regions

IDAWS-ORG-001
Severity
medium
Automation
Auto
Category
governance
Enforcementmandatory
Complexity / Impact
low(disruptive impact)
Risk Profile
medium likelihood(low residual)
Cloud Scopeaws:root
Environments
productionnon-productionsandbox
Target Resources
AWS::Organizations::Policy
Services
organizationsaccountcontrol-tower
Tags
governancescpregionsdata-sovereigntylanding-zone
Frameworks
NIST 800-53ISO 27001PCI DSSSOC 2
Governance
Cloud Security (quarterly)
Created
2026-05-03
Last Updated
2026-11-17

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.

Compliance Framework Mappings (4)

Regulatory baselines and industry standards mapped to this control specification.

Beta
Framework / StandardMapped Requirements & ControlsControls
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.

Audit Region-Deny SCPs, Attachments, and Enabled Regionsbash
# 1. Verify SCP policy type is enabled on Organization Root
root_id=$(aws organizations list-roots \
  --query "Roots[0].Id" \
  --output text)

aws organizations list-roots \
  --query "Roots[0].{Id:Id,ScpStatus:PolicyTypes[?Type=='SERVICE_CONTROL_POLICY'].Status | [0]}" \
  --output json

# 2. List custom SCPs attached to Root and inspect policy content and targets
aws organizations list-policies-for-target \
  --target-id "$root_id" \
  --filter SERVICE_CONTROL_POLICY \
  --query "Policies[?AwsManaged==\`false\`].{Id:Id,Name:Name,Description:Description}" \
  --output json

for pid in $(aws organizations list-policies \
  --filter SERVICE_CONTROL_POLICY \
  --query "Policies[?AwsManaged==\`false\`].Id" \
  --output text); do
  aws organizations describe-policy \
    --policy-id "$pid" \
    --query "Policy.{Id:PolicySummary.Id,Name:PolicySummary.Name,Content:Content}" \
    --output json
  aws organizations list-targets-for-policy \
    --policy-id "$pid" \
    --query "Targets[*].{TargetId:TargetId,Name:Name,Type:Type}" \
    --output json
done

# 3. Audit enabled and default regions in the account
aws account list-regions \
  --region-opt-status-contains ENABLED ENABLED_BY_DEFAULT \
  --query "Regions[*].{Region:RegionName,Status:RegionOptStatus}" \
  --output json

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

  1. Confirm the approved region list based on data residency, latency, and service availability requirements.
  2. 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).
  3. Create the region-deny SCP in the Management account and attach it to a sandbox or non-production OU first.
  4. Validate CI/CD pipelines, IAM Identity Center sessions, and Control Tower baselines, then attach the SCP to production OUs or Root.
  5. Disable unused opt-in regions per account using AWS Account Management.
Region Restriction SCP with Global Service Exemptionsjson
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "DenyAllOutsideApprovedRegions",
      "Effect": "Deny",
      "NotAction": [
        "a4b:*",
        "account:*",
        "acm:*",
        "aws-marketplace-management:*",
        "aws-marketplace:*",
        "aws-portal:*",
        "billing:*",
        "budgets:*",
        "ce:*",
        "chime:*",
        "cloudfront:*",
        "config:*",
        "cur:*",
        "directconnect:*",
        "ec2:DescribeRegions",
        "ec2:DescribeTransitGateways",
        "ec2:DescribeVpnGateways",
        "ecr-public:*",
        "fms:*",
        "globalaccelerator:*",
        "health:*",
        "iam:*",
        "importexport:*",
        "kms:*",
        "mobileanalytics:*",
        "networkmanager:*",
        "organizations:*",
        "pricing:*",
        "route53:*",
        "route53domains:*",
        "s3:GetAccountPublic*",
        "s3:ListAllMyBuckets",
        "s3:PutAccountPublic*",
        "shield:*",
        "sts:*",
        "support:*",
        "trustedadvisor:*",
        "waf-regional:*",
        "waf:*",
        "wafv2:*"
      ],
      "Resource": "*",
      "Condition": {
        "StringNotEquals": {
          "aws:RequestedRegion": [
            "eu-central-1",
            "eu-west-1"
          ]
        }
      }
    }
  ]
}
Deploy Region Restriction SCP via AWS CLIbash
# 1. Retrieve Organization Root ID and enable SCP policy type
root_id=$(aws organizations list-roots \
  --query "Roots[0].Id" \
  --output text)

aws organizations enable-policy-type \
  --root-id "$root_id" \
  --policy-type SERVICE_CONTROL_POLICY

# 2. Create and attach the region-deny SCP to Root
policy_id=$(aws organizations create-policy \
  --name 'DenyNonApprovedRegions' \
  --description 'Deny AWS actions outside approved landing zone regions' \
  --type SERVICE_CONTROL_POLICY \
  --content file://deny-regions-scp.json \
  --query "Policy.PolicySummary.Id" \
  --output text)

aws organizations attach-policy \
  --policy-id "$policy_id" \
  --target-id "$root_id"

# 3. Disable unused opt-in regions per account (example: ap-east-1)
aws account disable-region \
  --region-name ap-east-1

We value your privacy

We use analytics cookies to understand how visitors interact with our site and to improve the user experience. You can choose to accept or decline these cookies.