Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
directconnect_connection_redundancyProvider: AWS
Service:
directconnectSeverity: MEDIUM
Categories:
resilienceResource type:
OtherWhat this check verifies
AWS Direct Connect connectivity is provisioned with connection and location redundancy-multiple connections spread across at least two distinct Direct Connect locations in each Region.Risk
Missing connection/location redundancy creates a single point of failure, degrading availability. A router, fiber, or site outage can sever private paths to AWS, stalling app traffic, data replication, and admin access, leading to timeouts or extended downtime until alternate paths are restored.Recommendation
Apply redundancy and defense in depth:- Deploy 2 Direct Connect connections across two distinct locations
- Use dynamic, active/active routing for automatic failover
- Ensure provider/device diversity
- Size capacity so one link loss doesn’t overload remaining paths
- Consider a VPN as tertiary backup
Remediation
- CLI
- Terraform
- Dashboard steps
aws directconnect create-connection —region <REGION> —location <NEW_DX_LOCATION_CODE> —bandwidth 1Gbps —connection-name <example_resource_name>
References
- https://docs.aws.amazon.com/awssupport/latest/user/fault-tolerance-checks.html#amazon-direct-connect-location-resiliency
- https://repost.aws/knowledge-center/direct-connect-physical-redundancy
- https://aws.amazon.com/directconnect/resiliency-recommendation/
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = directconnect_connection_redundancy. 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