- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hello,
I suggest opening case with Support to check why that particular Tunnel is bouncing. It is possible that there was a version upgrade and/or there is an underlying issue with the VPN tunnel endpoint.
Please note AWS Site-to-Site VPN is a managed service, and periodically applies updates to your VPN tunnel endpoints. These updates happen for a variety of reasons, such as:
-
To apply general upgrades, such as a patches, resiliency improvements, and other enhancements
-
To retire underlying hardware
-
When automated monitoring determines that a VPN tunnel endpoint is unhealthy
https://docs.aws.amazon.com/vpn/latest/s2svpn/endpoint-replacements.html
One workaround would be to delete the VPN connection and recreate it, this will essentially spin up new VPN endpoints so that would rule out endpoint specific issues.
Lastly, please note, you can opt-out of tunnel endpoint related notifications, you would need to contact AWS support for the opt-out as well.
One good thing is that you have built HA - One VPN connection = 2 Tunnels so if there are issues with 1 Tunnel you have a backup path available.
Hope this helps.
Contenus pertinents
- demandé il y a 9 mois
- demandé il y a un an
- demandé il y a un an
- demandé il y a 3 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans