To help reduce your RDS costs, Amazon RDS allows you to stop and start your RDS instances. This is a very helpful cost-reduction technique that can be used in development, staging, or other environments where RDS instances do not need to be available 24/7.
Skeddly includes actions such as “Start RDS Instances” and “Stop RDS Instances” to help you automate this cost saving technique.
However, Aurora RDS clusters and instances cannot be stopped. They can only be terminated and recreated.
We have added a new action to Skeddly to help you lower your Aurora RDS costs by deleting and recreating your Aurora clusters. Our new action is called “Restore RDS Cluster”.
The new “Restore RDS Cluster” action will restore a fresh Aurora cluster from a cluster snapshot of your choosing. It will find appropriate RDS snapshots and use the most recent snapshot available.
There are many snapshot matching patterns:
Once a new Aurora cluster is restored, Skeddly will create an Aurora instance for the new cluster. You can choose the RDS instance class for this new instance, such as
The Aurora cluster and instance identifiers can be constant, or based on other run-time information, such as the current date. This means that your Aurora cluster can have a consistent endpoint, or a variable one.
Other options can be modified during the restore process as well:
Once the Aurora cluster has been restored, it can be accessed and used.
Then, you can optionally delete the cluster and it’s instances. The clean-up process will delete any RDS instances attached to the cluster (so you can attach more if desired), and finally the cluster itself will be deleted. When deleting the cluster, a final snapshot can be created. This allows you to save the data from your Aurora cluster for a later day.
This new action is available now. Pricing can be found on our pricing page.