2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
You can advertise 10.149.114.0/24 and 10.149.112.0/20 to the on-premises network if you use AWS Direct Connect gateway and transit gateway. In that case, you will have an option to configure any allowed prefixes that you want.
répondu il y a 8 mois
0
Hello.
If the VPC CIDR of "10.149.112.0/20" has already been advertised on the on-premises side, "10.149.114.0/24" is included and can be routed from on-premises to the VPC without problems.
The IP address range of "10.149.112.0/20" is as follows.
10.149.112.0 ~ 10.149.127.255
Thanks for the reply, Riku. I forgot to mention that 10.149.114.0/24 is needed to apply a policy routing when it's received by the on-prem router.
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a 2 mois
AWS OFFICIELA mis à jour il y a 3 ans- Comment connecter différentes succursales à l'aide de AWS Site-to-Site VPN et d'AWS Direct Connect ?AWS OFFICIELA mis à jour il y a un an
Thanks for the reply, Max. I am using AWS VGW to create the BGP peering. Is it possible to do the same as AWS Direct Connect gateway and transit gateway?
Happy to help, Cle. You need to use AWS Direct Connect gateway and transit gateway (TGW) for that. Check the "allowed prefixes" link that I posted. It has separate examples for a VGW and TGW that cover the scenario that you have.
If the response accurately and directly answers your question, please consider marking it as "accepted" to help other community members easily find information they are seeking.