Relational Database Service Charges How to Stop

If you're being charged for RDS despite having no active instances, there are several potential causes and solutions to investigate:

1. Check all AWS regions: RDS resources might exist in a region you don't typically use. Make sure to verify each region in your AWS account.

2. Look for hidden backups: Even if you don't see snapshots, check for automated backups that might still exist. These can incur storage costs even after instances are deleted.

3. Verify backup retention settings: If you previously had RDS instances, automated backups might be retained for a period after deletion.

4. Check for RDS Proxies: RDS Proxy services can incur charges even if you don't see the underlying database instances.

5. Use AWS Cost Explorer for detailed analysis: Filter by "Service" (select RDS) and "Usage Type" to identify exactly what's generating the charges. This will show you the specific RDS features causing the costs.

6. Look for the region in your bill: Your bill should indicate which region is generating the charges, which can help narrow down where to look.

7. Check for AWS Backup plans: There might be backup plans associated with your previous RDS resources that are still active.

If you've checked all these areas and still can't locate the source of the charges, contacting AWS Billing Support would be your best option. They can provide a detailed analysis of your account and help identify any hidden resources causing the ongoing charges.

You don't need to delete your account to stop these charges - the issue can be resolved by finding and removing the specific resources causing the fees.
Sources
To stop RDS from billing | AWS re:Post
I am still being charged for a AWS RDS even though i have deleted the database and any snapshots. | AWS re:Post
I would like to stop an active service and cannot find it | AWS re:Post
Amazon Relational Database Service charges - Amazon RDS Proxy | AWS re:Post