Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
vpc_different_regionsProvider: AWS
Service:
vpcSeverity: MEDIUM
Categories:
resilienceResource type:
AwsEc2VpcWhat this check verifies
Non-default VPCs are evaluated across the account to determine whether they exist in more than one region. The result reflects if your custom network topology is regionally distributed or concentrated in a single region.Risk
Single-region VPC deployment weakens availability and resilience. A regional outage, service disruption, or network control misconfiguration can cause broad downtime, hinder recovery, and increase the blast radius of incidents impacting business continuity.Recommendation
Adopt a multi-region network design:- Create VPCs in at least two regions for critical workloads
- Replicate routing, security controls, and endpoints consistently
- Apply fault tolerance and defense in depth with data replication and resilient DNS/failover to avoid single-region dependency
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws ec2 create-vpc —region <OTHER_REGION> —cidr-block <CIDR_BLOCK>
References
- https://docs.aws.amazon.com/vpc/latest/userguide/vpc-example-private-subnets-nat.html
- https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Scenario2.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = vpc_different_regions. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks