2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
You should only get those charges if you have an active RDS database instance. Have a look that Region those charges were for, and look in the RDS console under that region.
0
Thank you very much, skinsman. Obviously I purchased the wrong product. What do you mean with 'cols starts' ? Is it 'cold starts'? I will read about it. BR
beantwortet vor einem Jahr
Yes, sorry I meant "cold starts". There's a bit of info about it here in addition to AWS documentation - https://www.linkedin.com/pulse/coping-aurora-serverless-v1-cold-starts-web-steve-kinsman.
Please "Accept" my answer if this helps, to make it more visible to others seeking help.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
Thank you skinsman, yes I have an active database instance, and I am billed from Stcokholm which is correct. What surprises me is the amount of hours charged. I wonder if it is mandatory to explicitly close any kind of connection or thread in the javascript code, jusgt in case I am leaving these processes open. I can review the process list often, but that is not a solution... To connect, I use Jdbc.getConnection().createStatement().executeQuery
Thanks again
RDS pricing is bases on the number of hours your instance is running, it's nothing to do with connections made by clients. As soon as you create an instance you're charged the hourly rate for every hour it's running, so 24 hours per day even if no clients ever connect. You can stop a database temporarily (then you're charged only for storage) for up to a week but you have to start it again to use it.
If you can tolerate the cols starts and the MySQL version is suitable, you can use Aurora Serverless v1 which can scale down to 0 when not in use.