Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Each subnet must reside entirely within one Availability Zone and cannot span zones

VPC to Customer premises:

AWS Direct Connect or

VPN connections from on-premises


connecting VPCs in different AWS Regions using either

AWS-managed networks or

non-AWS networks ( Private network/Internet-ISP = AWS Direct Connect or VPN connection )


Single Region Multi-VPC Connectivity

https://aws.amazon.com/answers/networking/aws-single-region-multi-vpc-connectivity/


Multiple Region Multi-VPC Connectivity

https://aws.amazon.com/answers/networking/aws-multiple-region-multi-vpc-connectivity/

VPC Peering

networking connection between two VPCs  ( between your own VPCs ( same/different Region)  or  with a VPC in another AWS account )

https://docs.aws.amazon.com/AmazonVPC/latest/PeeringGuide/peering-configurations-full-access.html#two-vpcs-full-access




  • No labels