Course contentsShow
← Security
Lesson 1842 of 3,05237. Cloud Security - Network ArchitectureFree lesson

Cross-Region and Cross-Account Connectivity

Securely connecting VPCs across different regions and AWS accounts using peering and transit options.

Cross-Region and Cross-Account Connectivity

What you'll learn: How to securely extend your cloud network across AWS regions and separate AWS accounts while maintaining strong isolation and control.

The Challenge of Distributed Cloud Architectures

As organizations scale, they often need resources in multiple AWS regions (for disaster recovery, latency optimization, or compliance) or across separate AWS accounts (for organizational boundaries, cost management, or subsidiary isolation). The question becomes: how do you connect these distributed networks securely?

Connection Options

You have several tools from your security toolkit:

VPC Peering Across Boundaries

VPC Peering works across both regions and accounts. To peer cross-account, you create a peering connection request from one account and accept it in another—both owners must explicitly agree. This maintains the principle of least privilege: each account controls its own security groups and NACLs, and neither side automatically trusts the other's traffic.

Transit Gateway for Complex Topologies

Transit Gateway also supports cross-region and cross-account connectivity. You can create Transit Gateway peering connections between regions or share a Transit Gateway across accounts using AWS Resource Access Manager (RAM). This centralizes routing control while maintaining security boundaries.

Security Considerations

  • Route Table Precision: Only advertise specific CIDR blocks you intend to share—never full RFC 1918 ranges unnecessarily
  • Security Group Referencing: Cross-account security group references require both accounts' cooperation and AWS resource sharing
  • Monitoring: VPC Flow Logs capture cross-region and cross-account traffic for audit trails
  • Cost and Data Transfer: Cross-region connectivity incurs data transfer charges—factor this into your security architecture

Think of it like international trade agreements: both countries (accounts/regions) must explicitly agree to the connection terms, inspect what crosses borders, and maintain sovereignty over their territory.

Key Takeaway: Cross-region and cross-account connectivity extends your network architecture across boundaries using VPC peering or Transit Gateway, but security controls, explicit approvals, and monitoring remain critical to prevent unintended access.