Stay up to date with the latest from the Knowledge Center. See all new and updated Knowledge Center articles published in the last month and re:Post’s top contributors.
RDS Serverless MYSQL is billing than expected
I have created a dev and a production instance of the RDS Serverless Aurora MYSQL by selecting ACU min to 0.5 and max to 16 and have been processing data.
In the month of June, July , I have just created 700 records inserted and processed in the database. where it is one time process and the data is very minimal.
But the charges are around 500$ + for this simple operation.
I have also created elastic cache as per the recommendation while installing the database and that accounts to 80 + $
is the RDS charged when not in use as well? What could be the result of this unexpected charges. Did anyone face similar issue? Could you please guide me here!
- Newest
- Most votes
- Most comments
Hi, yes Aurora Serverless v2 is charged when not in use - unlike v1 it never scales down to 0. It will continue to charge you 0.5 ACU, which over 2 months would be about 730 ACU-hr.
However you've been charged 2885.123 ACU-hr, so your database has been scaling up over 0.5 ACU a fair bit (or you have more than one database running). I'd suggest having a look at the metrics in CloudWatch for your database and seeing how it has responded at the times you were processing records.
Also I see you've enabled RDS Proxy. At https://aws.amazon.com/rds/proxy/pricing/ you can see that this has a minimum charge of 8 ACUs, so over 2 months about 2 x 730 x 8 ACU-hr = 11680 ACU-hr. Your bill shows 23040 ACU-hr, so maybe you've created two RDS Proxy instances?
Relevant content
- asked 6 years ago
AWS OFFICIALUpdated 4 months ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago
Thanks for the response. I am using 2 servers one is for dev and other is for prod. I will check the CloudWatch and see the history. Will keep posted after verifying the sever configurations and validating logs. Thanks