Idle NAT Gateway
A NAT gateway bills per hour from creation to deletion, independent of the bytes it processes.
Free to start. No card. The playground just needs your work email.
AWSAzure
Found, explained, fixed.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS and Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Delete idle NAT gateway. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
After a guided review, where you confirm the change, ZopNight deletes the resource, then checks the change took.
- Applies to
- NAT Gateways on AWS, NAT Gateways on Azure
- The fix, by hand on AWS
- Verify no subnets route through this NAT Gateway.
- Check if private instances still need outbound internet access.
- If idle, delete the NAT Gateway.
- Update route tables to remove the NAT gateway route.
- Consider VPC endpoints for AWS service access instead.
ZopNight does this for you after a guided review.
- 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 IDs
RC-011RC-1383- 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.