AWS Site-to-Site VPN increases service quotas for route limits
AWS Site-to-Site VPN service today increased the default service quotas for the dynamic routes advertised to and from a Site-to-Site VPN connection on a Transit Gateway. You can now advertise up to 1,000 dynamic routes (an increase from 100) from a customer gateway device to a Site-to-Site VPN connection on a Transit Gateway. Similarly, you can now advertise up to 5,000 routes (an increase from 1,000) from a Site-to-Site VPN connection on a Transit Gateway to a customer gateway device. Advertised routes come from the route table that's associated with the VPN attachment.
AWS Site-to-Site VPN service today increased the default service quotas for the dynamic routes advertised to and from a Site-to-Site VPN connection on a Transit Gateway. You can now advertise up to 1,000 dynamic routes (an increase from 100) from a customer gateway device to a Site-to-Site VPN connection on a Transit Gateway. Similarly, you can now advertise up to 5,000 routes (an increase from 1,000) from a Site-to-Site VPN connection on a Transit Gateway to a customer gateway device. Advertised routes come from the route table that's associated with the VPN attachment.
The new limits apply in US East (N. Virginia), US West (N. California, Oregon), and EU (Ireland) Regions today with the following AWS Regions coming on April 9th 2021: US East (Ohio), Africa (Cape Town), Europe (Frankfurt, London, Paris, Stockholm, Milan), Asia Pacific (Hong Kong, Singapore, Tokyo, Sydney, Seoul, Mumbai, Osaka), Canada (Central), South America (São Paolo), and Middle East (Bahrain). The higher limits are reflected in your accounts for all new VPN connections. You can opt-in your existing VPN connections by using the modify VPN connection option. These new limits apply only for Site-to-Site VPN connections on a Transit Gateway and does not apply for Site-to-Site VPN connections on a virtual private gateway. For more information, please see the AWS Site-to-Site VPN quotas documentation.