Optimizing Cloud Costs: AutoStop Database Instances Based on Application Traffic



This article refers to AWS RDS databases, but the same principles are applicable for other database instances.

As organizations continue to leverage cloud infrastructure, the need for efficient resource allocation and cost optimization becomes increasingly important. One of the ways to achieve this is by ensuring that database instances are only running when necessary. However, databases typically lack load balancers, making it challenging to measure their traffic. In this article, we will discuss how to set up dependencies between AutoStopping Rules to manage database instances according to application traffic.

Understanding Dependencies Between AutoStopping Rules

AutoStopping Rules can be configured to work in tandem, allowing you to manage multiple cloud resources based on their relationships. When one Rule receives traffic, it can activate or deactivate other Rules, effectively managing resources according to the current demand.

For example, consider an application server dependent on a database server. To optimize costs, you can create two Rules: one for the application server and another for the database server. By setting the Rule managing the application server to be dependent on the Rule managing the database server, you ensure that the database server is only active when the application server receives traffic.

Implementing AutoStopping Rules for Database Instances

Follow these steps to create and manage AutoStopping Rules for your database instances:

  1. Analyze your application and database infrastructure: Determine the relationships between your application servers and database instances, as well as any interdependencies between them.
  2. Create AutoStopping Rules: Using the Harness Cloud Cost Management platform, create AutoStopping Rules for each of your application servers and database instances. For more information, refer to the Harness documentation on creating AutoStopping Rules for RDS.
  3. Set dependencies: Configure the dependencies between the Rules, ensuring that the Rules managing application servers are dependent on the Rules managing the database instances.
  4. Review and adjust: Regularly review your AutoStopping Rules to ensure that they are effectively managing resources and optimizing costs. Make adjustments as needed based on your application’s requirements and usage patterns.
  5. Monitor performance: Use the Harness AutoStopping Dashboard to monitor the performance of your AutoStopping Rules and gain insights into resource utilization and cost savings.


By setting up dependencies between AutoStopping Rules, you can optimize cloud costs and resource allocation for both application servers and database instances. This approach ensures that your database instances only run when needed, preventing unnecessary expenses and reducing overall cloud costs. For more information on Harness Cloud Cost Management and AutoStopping Rules, consult the Harness documentation and optimize your cloud infrastructure today.

Useful links