Hybrid Cloud is the preferred approach with ‘Cloud first’ policy for most of the organizations. Many large enterprises have a need to establish secured hybrid cloud connectivity topology across
- Cloud accounts & its VPCs(Virtual Private Cloud)
- Office on premise across geo locations.
It is also essential that the network connectivity design, address the need for the isolation of North South and East West traffics based on business / compliance needs is also critical. In this post, we’ll look at the design choices we have and how AWS Transit Gateway can help simplify and enable well architected network design on cloud.
Network connectivity design is one of the most significant aspects that one needs to get it right from the beginning of any design strategy before provisioning any resources in cloud. From infra network setup point of view, creating and managing multiple IPSec tunnels/peering / direct connect(DX) among accounts and VPC will become more complicated over time and with every addition of a component.
A Customer Scenario
Let us take the case of the customer whose needs warranted to have distinct AWS account for deployments of Prod and Dev resources. To start with the connectivity requirements was to link up 3 corporate (locations & DC co-locations) and the existing current cloud workloads. There was also a need to have VPC peering connections between Prod and Dev accounts and also to their partner’s VPC in another AWS account in the same region.
Customer insisted a centralized approach of connectivity that could help maintain and enhance this to future new locations and accounts with ease and simplicity.
