> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/cloud-cost-management/cost-optimization/autostopping-rules/1-auto-stopping-rules.md).

# Overview

AutoStopping Rules make sure that your non-production resources run only when used, and never when idle.

## What are AutoStopping Rules? <a href="#what-are-autostopping-rules" id="what-are-autostopping-rules"></a>

Cloud resources in non-production environments (dev, test, staging) are typically used for only 30-40% of the time they're running, yet you pay for 100% of that time. AutoStopping Rules ensure you're only **paying for resources when they're actually in use**.

AutoStopping Rules let you define:

* **Controlled resources**: Choose exactly which EC2 instances, Auto Scaling Groups, Kubernetes namespaces, RDS databases, or other supported assets the rule should manage.
* **Idle-time threshold**: Specify how long a resource must remain inactive before AutoStopping considers it idle and eligible for shutdown.
* **Optional fixed schedules**: Keep resources online during business hours, maintenance windows, or any recurring schedule you choose.
* **Dependency order**: List upstream and downstream services so AutoStopping stops and starts them in the right sequence.
* **Access method**: Select load balancer, proxy, or direct IP so your teams continue to use the same DNS, SSH, or RDP endpoints without interruption.
* **Set-and-forget automation**: Zero manual overhead after initial setup

***

## What's Supported? <a href="#whats-supported" id="whats-supported"></a>

| Cloud Provider                                                                                                                                                                                                                                                                         | Supported Resources                                                                                                   |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| <p><img src="https://1217180450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO2HVWkYMptNUG08jo8hr%2Fuploads%2Fgit-blob-ecfcfc08d4eeff8fa10621d11791cadfd152edee%2Faws-logo.svg?alt=media" alt="AWS" data-size="original"></p><p> <strong>AWS</strong></p>       | <ul><li>EC2</li><li>Auto Scaling Groups</li><li>Kubernetes (EKS)</li><li>ECS Services</li><li>RDS Instances</li></ul> |
| <p><img src="https://1217180450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO2HVWkYMptNUG08jo8hr%2Fuploads%2Fgit-blob-445315a5debd28fa28f7802b1e64f2467198e94b%2Fazure-logo.svg?alt=media" alt="Azure" data-size="original"></p><p> <strong>Azure</strong></p> | <ul><li>On-demand VMs</li><li>Kubernetes Clusters (AKS)</li></ul>                                                     |
| <p><img src="https://1217180450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO2HVWkYMptNUG08jo8hr%2Fuploads%2Fgit-blob-657b3b27a8ff7f0190589440322ab7f131ba2ade%2Fgcp-logo.svg?alt=media" alt="GCP" data-size="original"></p><p> <strong>GCP</strong></p>       | <ul><li>GCE VMs</li><li>Kubernetes Clusters (GKE)</li><li>Instance Groups</li></ul>                                   |

***

## How AutoStopping Works <a href="#how-autostopping-works" id="how-autostopping-works"></a>

AutoStopping intelligently manages your cloud resources through a seamless four-step process:

1. **Intelligent Detection**: Resources are continuously monitored for user activity and workload patterns
2. **Automatic Shutdown**: Once your configured idle threshold is reached, resources are safely stopped to eliminate wasted spend
3. **Seamless Restart**: When access is requested, resources are automatically restarted based on your dependency configuration
4. **Transparent Access**: End users continue using the same familiar endpoints (DNS, SSH, RDP) with minimal interruption

AutoStopping offers:

* **Unlimited rules and resources**: Create as many rules as needed with no restrictions
* **Unlimited dependencies**: No limit on the number of dependencies a rule can manage
* **Flexible configuration**: Customize idle time thresholds, schedules, and access methods
* **Resource-specific restart times**:
  * RDS instances: Warm-up time depends on cluster/instance size (\~25 minutes)
  * Other resources: Typically warm up in under 2 minutes (max 5 minutes)

***

## Ready to Get Started? <a href="#ready-to-get-started" id="ready-to-get-started"></a>

Follow our [Set Up AutoStopping Rules](/cloud-cost-management/cost-optimization/autostopping-rules/autostopping-rules.md) to set up AutoStopping in your environment in three simple step.

{% @harness-feedback/feedback %}