Case 4: RDS DB Instances

Scheduling start and stop of RDS instances help to significantly save costs. We will schedule all RDS Instances in the Dev environment to run from 09:00 to 18:00 on Monday to Friday.

.

You can stop a DB instance for up to seven days. If you don't manually start your DB instance after seven days, your DB instance is automatically started so that it doesn't fall behind any required maintenance updates.

.

You can stop only MariaDB, Microsoft SQL Server, MySQL, Oracle and PostgreSQL instances

.

  1. Create a new schedule and set your timings (09:00 to 18:00, Monday to Friday)

.

  1. Choose RDS as the service and DB Instances as the resource. Choose Tags For Resource from Add-Ons.

.

  1. Set the filter to pass through all DB Instances with the tag env set to dev

.

  1. Set the parking action to stop DB Instances

.

  1. Set the unparking action to start DB Instances

.

  1. Save and deploy the workflow

Did You Find This Article Helpful?

Case 3: Instances in ASG (Without Termination)

Case 5: Redshift Clusters

Powered by HelpDocs