Help Docs

Start, stop, and reboot with failover the RDS DB instances

With Site24x7's IT Automation framework you can create an action profile to automatically start, stop or reboot with failover the monitored Amazon Relational database instances in response to events. You can trigger the automation in response to various alert events happening in your monitored AWS environment; metric exceeds the defined threshold value; or for monitor level changes like Up/Down/Trouble.

Required Permissions

Please ensure the following read level permissions are present in the policy attached to the Site24x7 IAM entity/IAM Role created.

  • "rds:RebootDBInstance"
  • "rds:StopDBInstance"
  • "rds:StartDBInstance"


  • You can't stop or reboot the DB instance if it is not in an "Available State"
  • Actions can only be executed on those DB instances that are monitored by Site24x7
  • All the limitations applicable within AWS for stopping a DB instance - Multi-AZ deployment, Read replica and 7-day stop period is applicable here as well.

Create an action profile 

  • Login to the Site24x7 web console, Select Admin > IT Automation Templates
  • Click on the drop down list and select "Start/Stop/Reboot with Failover RDS" as type
  • Type in an unique name in the Display Name field for identification purpose.
  • Next, click on the drop down and choose the list of monitored RDS DB instances, where you want the action to be performed.
  • Max Allowed Action Execution Time: The maximum number of seconds Site24x7 has to wait before the request times out. You can enter a value within the range 1- 90 seconds.
  • Send the Automation Result via Email: You can choose to receive an email regarding the automation result, by setting the toggle button to Yes. Share automation results via an email to your User Alert Group configured in the Notification Profile. This email will contain parameters including the automation name, type of automation, incident reason, destination hosts, and more.
  • Save the profile.

Simulate the Automation

Before mapping the action profile, you can test its functionality by invoking the action manually within the Site24x7 console or by using our REST APIs. This is done to check whether appropriate write level permissions are provided or not. Once you've created the profile, navigate back to the IT Automation summary page (Admin > IT Automation) and click on the  to execute a test run.

Map the Action Profile

To execute the automation, map the action profile to an desired alert event. You can either map the profile to a predefined monitor level event type or to an custom attribute level event type (database connections < 10).

Monitor level mapping

Navigate to the Edit monitor page (“RDS instance monitor page" > > Edit) of the monitored RDS DB instance, and map the action profile with any of the following monitor status changes.

  • Execute on Down
  • Execute on Up
  • Execute on Trouble
  • Execute on any Status Change

Attribute level mapping

You can also associate the action profile to RDS related metric data points like CPU usage, connections, read write IOPS and more. Navigate to the Edit threshold profile page of the monitored RDS DB instance (Navigate to the Edit Monitor page of the resource > click on the Pencil icon adjacent to the Threshold and Availability field) and map the profile to any desired attribute by clicking on the  "Select Automation to Execute" field.

Use case

Stop underutilized RDS DB instances or instances running in your test or development environment, to reduce usage hours and improve cost savings.

Was this document helpful?

Would you like to help us improve our documents? Tell us what you think we could do better.

We're sorry to hear that you're not satisfied with the document. We'd love to learn what we could do to improve the experience.

Thanks for taking the time to share your feedback. We'll use your feedback to improve our online help resources.

Shortlink has been copied!