Geek Answers Handbook

Aurora RDS screen cannot be stopped

I am trying an instance of Amazon Aurora and I see no way to stop it. The only options are Delete and Reboot.

I'm missing something.

+8
amazon-web-services amazon-rds-aurora
source share
3 answers

Edit: RDS can be stopped / started from 2017/06/01, for this announcement , but does not yet support Aurora.

In the AWS console, the Stop option is mentioned in the same menu as in the body of the question. A stopped instance retains its storage, but cannot be modified until it starts again. Instances cannot be permanently stopped - after seven days the stopped instance will automatically start again.

Unfortunately, some configurations still do not support this feature. See below for a break for an alternative.

Additionally see

Alternative suggestion for incompatible configurations:

It includes:

  • Aurora
  • Old SDKs until June 2017.
  • RDS with Multi-AZ
  • Read-Only RDS
  • RDS with SQL Server Mirroring

RDS instances in these situations cannot be stopped and started by default, like an EC2 instance. However, you can approach this behavior by deleting the RDS instance with the final snapshot, and then come back later to restore the RDS instance from this database snapshot.

This is approaching a “stop”, because new data will not be recorded after your last shot, and you will not pay for the current instance of RDS. Just as you pay for any volumes of EBS connected to your stopped EC2 instance, you will also continue to pay for storing the database snapshot during its existence.

This behavior diverges from stopping the EC2 instance in that the underlying infrastructure will no longer exist. When restoring from a snapshot, it will be on a new RDS instance, and it will take some time to restore, depending on the size of your infrastructure and the snapshot.

additional literature

+7
source share

They added support for stopping / starting RDS instances this month (June 2017). The key bit of information from the @Venkata link is: "The stop / start function is available for database instances running Single-AZ deployments that are not part of the Read Replica configuration (both source and replica)."

This means that it does not work for Aurora, since the default is Multi-AZ. You do not even get this option in the interface.

It will also not work for MySQL if a readable replica is configured. You will not receive the option on the slave, and you will receive the option on the master, but it will not work if you try to use it.

You can achieve the same thing as when restoring from a snapshot ... but the bottom side takes about one hour with our large db instance, while stopping it and starting it can happen after ~ 5 minutes.

+5
source share

They just added support for this today:

https://aws.amazon.com/about-aws/whats-new/2017/06/amazon-rds-supports-stopping-and-starting-of-database-instances/

Enjoy! :)

+1
source share

More articles:


All Articles