- Newest
- Most votes
- Most comments
There is no way to disable the VPN so it can be enabled later on, instead you can disable the tunnels on the on-prem side so the on-prem side can forward traffic over the primary, and enable the tunnels later when needed, but you'll still be charged for the VPN connection which is about $36 per month.
Or you can have both VPNs (primary and backup) configured and both are active, and through BGP attributes you can have one act as a primary and one as secondary, for that you would need to use dynamic VPN instead of static.
As per the other answer, you can't put a VPN connection into a disabled state.
Something I created a few years ago was a Lambda function that would create a VPN connection when specific conditions were met - for example, when a network link goes down. It might be useful here: https://github.com/Brettles/NetworkBreakGlass
Relevant content
- Accepted Answerasked 4 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 5 months ago
Thats a nice alternative, thanks for the function, very usefull!