RDS Instance Publicly Accessible
The database answers on a public endpoint, so the only thing standing between it and the internet is the password.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Disable public accessibility on RDS instance.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- RDS Instances on AWS
- The fix, by hand
- Identify every client that uses the public endpoint (search application config / secrets store / CI vars).
- Migrate clients to the VPC endpoint (or to a VPN / Transit Gateway path).
- Open RDS → Databases → select this instance → Modify.
- Connectivity → Public access = Not publicly accessible.
- Apply immediately; tighten the inbound security group to private CIDRs only.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-085- Full reference
Related checks
See the compliance findings 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.