VPN Connection Idle, No Tunnels Up
A VPN connection bills per connection-hour for as long as it exists, and one with no tunnel up is billing while carrying no traffic at all.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Delete the VPN connection with no tunnels up. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- VPN Connections on AWS
- The fix, by hand
- VPC → Site-to-Site VPN connections → the resource → check Tunnel status. Confirm both tunnels DOWN.
- Confirm the on-prem customer gateway is decommissioned (network ops sign-off).
- Note the attached Virtual Private Gateway / Transit Gateway. These may need cleanup separately.
- Actions → Delete VPN Connection → confirm.
- If the VGW is unused after deletion: Virtual Private Gateways → detach from VPC → Delete.
These are the steps the finding carries in the product.
- Category
- Idle resources. Resources running but doing no useful work: zero invocations, no connections, no traffic.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-162- Full reference
Related checks
See the idle resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.