Idle RDS Proxy, No Connections
An RDS Proxy bills per vCPU of the database it fronts, per hour, whether or not any client connects through it.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, fixed.
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 idle RDS proxy. 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
- RDS Proxies on AWS
- The fix, by hand
- Search application code / Lambda env vars / Secrets Manager for the proxy endpoint hostname.
- If references exist, update them to the direct RDS endpoint and confirm clients reconnect.
- Open RDS → Proxies → select → Actions → Delete.
- Confirm by typing the proxy name.
- Validate billing drop 24h later.
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 ID
RC-170- 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.