By using AWS re:Post, you agree to the Terms of Use

AWS RDS doesn't seem to be stopping even after terminating the instance; (added a screenshot)


I am a beginner in using AWS. I was able to make use of the AWS documentation for setting up EC2 and RDS for deploying my personal website using the Free Tier quota. After I was done using the service I stopped both the instances. Towards the end of the month, even after I stopped both the instances, I was sent an alert regarding the 85% usage of my Free Tier quota. So I checked the AWS Billing (screenshot added below) and tried finding where the RDS was taking up over 17GB of data out of max limit of 20GB. To me this is not making sense as I had already terminated the RDS instance. Also, I did not opt for snapshots. If you can spot what I'm doing wrong here— thank you!

Link for screenshot:

2 Answers
Accepted Answer

Post Update:

My issue has been resolved!

Here's what had happened:- I was sent an email regarding 85% usage of my AWS resource for Free Tier. This was a day during the month of June. Right after, I immediately headed to stop all my instances. After that it still didn't seem to have stopped because the dashboard kept showing the updated usage limit which happened to keep increasing day after day. After the month got over, the very next day, on the 1st of July the dashboard cleared out with all instances gone! Wiped away. Cleared. Relief. Finally. Phew!! End of story.

answered a month ago


I understand that you launched two instance EC2 and RDS for deployment of your personal website using the Free Tier quota, and even after you stopped both of them you were still charged towards the end of the were also sent 85% usage of your free tier. Please correct me if I misunderstood you.

Please note that while your DB instance is stopped you are charged for provisioned storage (including Provisioned IOPS) and back storage(including manual snapshots and automated backups within your specified retention window), but not for DB instance hours. For more information, see Billing FAQs[1].

The Free Tier isn't a special mode or type of instance in RDS, it is a credit that is applied at the end of the month if you are within your first year of the account's life. So during normal RDS operation it has no idea if an RDS instance is "free" or not. At the end of the month the billing system applies a credit of up to 750 hours of t2.micro time and 20GB of storage & snapshot storage to the account.

Also, take note that if you chose to have Amazon RDS create a final DB snapshot before it deletes your DB instance, this snapshot might be the one incurring charges. However, you may delete the delete DB snapshots managed by Amazon RDS when you no longer need them[2].

Further, if you ran an EC2 instance at the beginning of the month but you stopped or terminated it later ,then your bill will include charges for the time that the instance was running. For more information about why you being charged for EC2 when you all instance were terminated refer to this article[3].

I hope I was able to help, Thank you.

Reference Links:

[1] Amazon RDS FAQs-

[2] Deleting a DB snapshot-

[3] Why am I being charged for Amazon EC2 when all my instances were terminated?-

answered 2 months ago
  • Regarding snapshots— I have checked and can verify that I did not opt for any snapshots. Also I have previously already gone through the respective reference links that you've provided. None of them contained an explanation for my problem hence I thought of posting my query here. Thanks for looking into it anyways. I'll keep waiting for the solution to the problem.

  • hello, Thank you for getting back to me.

    I Acknowledge you waiting for solution ,however in terms of billing being incurred i have provided the information.

    The accounts team will be able to see if the resources are in the account and the reason you are still accruing charges. Please contact AWS billing[1] for more detailed information about the unexpected charges after terminating the resources.

    Reference link


You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions