We have several AWS accounts, each with a few VPCs, and the number of connections is starting to get awkward to manage. Some workloads need to communicate across accounts, but plenty should remain isolated.
At what point did you move from VPC peering to Transit Gateway? I’m especially interested in how you weighed route management and operational simplicity against the added cost, and whether Transit Gateway route tables made it easier to control cross-account VPC connectivity.
Can you answer this question?
Write Answer0 Answers