AWS RDS stop an instance – A Step-by-Step Guide

Published on August 21, 2018
Share this on

Under normal circumstances starting or stopping an RDS is simple, but what one may come across is finding an unexpected line entry in the bill for an RDS that they thought was stopped. Stopped RDS instances are automatically started for you if they remain in the stopped state for 7 days. While an RDS is in a stopped state, the storage accrues cost along with any EIP associated and snapshots.

Best practices are if utilization patterns (i.e number of connections to the RDS) drops significantly downshifting the RDS instance type to reduce costs. If the number of database connections for 3 or more days is low, CloudSqueeze will inform you to consider stopping the instance. If an RDS is not in use, rather than just stopping it consider taking a manual snapshot of that instance and delete the instance altogether. When you terminate an RDS instance in the AWS console, AWS will ask if you want to take a final snapshot prior to terminating the RDS. When you RDS application is ready to be used in the future, you can bring up your RDS from this snapshot and this approach will give you the least cost, relative to just stopping and restarting.

Stopped RDS instances are automatically started for you if they remain in the stopped state for 7 days. While an RDS is in a stopped state, the storage accrues cost along with any EIP associated and snapshots.

RDS engines running MySQL, MariaDB, Postgresql, Oracle and SQL server can be stopped via command line or from the RDS console of AWS easily unless you have one of these at play:

  1. You are attempting to stop a DB instance that has a Read Replica, or has is a Read Replica setup
  2. You are attempting to stop a DB instance that is in a Multi-AZ deployment.
  3. If you are using Microsoft SQL Server Mirroring on SQL server, you cannot stop it.
  4. If your instance is already stopped, there are limitations on altering option groups and other DB parameters in this state

To stop a DB instance

  1. Sign in to the AWS Management Console and open the Amazon RDS console a search for RDSFind RDS in AWS Console
  2. In the navigation pane, choose Instances, ensure you are in the right region where your instances are deployedrds instances and region
  3. Choose Instance actions, and then choose Stop.select an RDS
  4. You can choose to take a snapshot of your RDBMS before stopping if you wishRDS stopping
  5. Choose Yes, Stop Now to stop the DB instance and in a few minutes the status of the RDS will change from stopping state to stopped state like this:rds is stoppingstopped state of an rds

To terminate an RDS

  1. Take a final snapshot as part of stopping the instancestop an rds
  2. Then once the instance is in a stopped state, you can delete the RDS:delete an rds
  3. You can choose to take another final snapshot or skip that by acknowledging you have a snapshot.final rds snapshot
  4. Watch to see that the status changes from deleting to deletedrds is deleted

If you encounter issues in the process of stopping an RDS or terminating a stopping an RDS instance or have a question about any of our AWS Tutorials, please reach out to us with a comment and will add this to the FAQs. If you would like to partner with us and develop AWS open source scripts for these steps, reach out to us.

Watch a video on the steps to stop an RDS here:

If you encounter issues in the process of stopping an RDS or terminating a stopped RDS instance or have a question about any of our AWS Tutorials, please reach out to us with a comment and will add this to the FAQs. If you would like to partner with us and develop AWS open source scripts for these steps, reach out to us.

Download the whitepaper that explains why cloud capacity planning needs a different thought process from traditional on-premise infrastructure.

We wont spam you or sell your email address

Learn more