Moving to AWS Transit Gateway from VPC Peering
How would an organization that currently uses VPC peering move to Transit Gateway given that the same routes that currently exist between VPC peers would need to be set up for Transit Gateway routing.
You can use Serverless Transit Network Orchestrator to deploy hub and spoke model using Transit Gateway. There's an option to add Route to TGW, this will add route to VPC route table associated with the subnet but it will not overwrite existing route. So if you have route going to VPC peering that will not get overwritten.
You can deploy this and have default route or wider CIDR range (less specific route) under Default Route to TGW
Example if you have 10.1.0.0/24 -- VPC-peer1
and 10.2.0.0/24 -- VPC-peer1
in VPC route table, you can have 10.0.0.0/8
under Default Route to TGW. Once the solution is deployed and you have correct route in place, you'll have to manually delete VPC peering route.
Relevant questions
AWS Transit Gateway attachment pricing
Accepted Answerasked 2 years agoTransit Gateway to Direct Connect Gateway to Transit Gateway
Accepted Answerasked 2 years agoAWS Transit Gateway peering encryption
Accepted Answerasked 2 years agoTransit Gateway Inter-region Peering Pricing
Accepted AnswerAccessing S3 Gateway VPC Endpoint from another VPC (VPC Peering established between both source and destination VPCs)
Accepted Answerasked 2 years agoTransit gateway & VPC peering - IP forwarding
Accepted Answerasked 2 years agoTransit Gateway Peering - Cross Accounts Not Sharing Payer ID
Accepted Answerasked 2 years agoMoving to AWS Transit Gateway from VPC Peering
Accepted Answerasked 2 years agoCross Region private link
Accepted Answerasked 3 months agoMigration from Transit VPC to AWS Transit Gateway
Accepted Answerasked 2 years ago