- Newest
- Most votes
- Most comments
I'd suggest you to go to Cost Explorer and see what you find there
-
Go to Cost Explorer
-
Choose Dimension as Usage Type
-
Select Service as Relation Database Service
-
Apply filter Usage Type
See, what this shows for that same time period. Next, change the filter from "Usage Type" to "API Operation" and see what are the contributors. Keep doing the same exercise by changing the filters to Region, Availability Zone, Charge Type. One or the other filter would definitely give you the lead where that charge is coming from.
Additional Reference: RDS Pricing
Comment here if you have additional questions, happy to assist.
Abhishek
I, ah, figured it out. I did not see the region on the top right next to my name.... I was looking really hard for the region on the menu on the left. But its right there in the top left. Thank you for taking the time to read my question.
Hi Joop, 🤗
Quick Checks:
-
Check for Orphaned Resources:
- Make sure there are no remaining RDS resources in the Ohio region, such as:
- Manual Backups: Even if snapshots are deleted, manual backups might still exist.
- Reserved Instances: You might have reserved instances or other commitments that are still active.
- Cluster Endpoints: Ensure there are no active cluster endpoints or related resources.
- Make sure there are no remaining RDS resources in the Ohio region, such as:
-
Switch Regions in the Console:
- In the AWS Management Console, switch to the Ohio region specifically to review any remaining resources. Sometimes, resources are tied to a specific region that you might not see by default.
-
Check the Billing Dashboard:
- Visit the AWS Billing Dashboard and review your charges. This can help you identify what exactly is causing the charges.
-
Look at Cost Explorer:
- Use AWS Cost Explorer to filter by service and region. This can give you a breakdown of charges and help you pinpoint the cause.
Hope this helps! 😁
Relevant content
- asked 4 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago