AutoStopping Rules FAQs

Updated 1 week ago by Archana Singh

This article addresses some frequently asked questions about Harness intelligent cloud AutoStopping Rules:

AWS

What are AutoStopping Rules?

AutoStopping Rules make sure that your non-production resources run only when used, and never when idle. It also allows you to run your workloads on fully orchestrated spot instances without any worry of spot interruptions. For more information, see AutoStopping Rules Overview.

How do AutoStopping Rules access the AWS VMs?

The VMs can be accessed using any of the following methods:

  • DNS Link
  • SSH/RDP

For more information, see Setup Access Using DNS Link and Setup Access Using SSH/RDP.

Do AutoStopping Rules need a load balancer like Application Load Balancer (ALB) for non-prod workloads?

Yes, you need to create an Application Load Balancer (ALB) for AWS. A load balancer serves as the single point of contact for clients. The load balancer distributes incoming application traffic across multiple targets, such as EC2 instances, in multiple Availability Zones. This increases the availability of your application.

An Application Load Balancer makes routing decisions at the application layer (HTTP/HTTPS), supports path-based routing, and can route requests to one or more ports on each container instance in your cluster.

For more information, see Create an Application Load Balancer for AWS.

Can I use Route 53 as my DNS provider?

You can use Amazon Route 53 as the DNS service for your domain, such as example.com. When Route 53 is your DNS service, it routes internet traffic to your website by translating friendly domain names (such as www.example.com) into the numeric IP addresses (such as 192.0.2.1) that computers use to connect to each other.

For more information, see Create an Application Load Balancer for AWS.

Can I use any other DNS provider other than Route 53?

Yes, you can use other DNS providers like GoDaddy, HostGator, and so on to map your custom domain to the hostname. For more information, see Create an Application Load Balancer for AWS.

Can I use AutoStoping Rules to manage my resources hosted in the AWS GovCloud?

Currently, the resources hosted in the AWS GovCloud regions cannot be managed using AutoStopping Rules.

How AutoStopping Rules can help when I shut down my VMs during non-working hours?

Before Cloud AutoStopping, the only other option to solve these problems was the use of static resource schedulers (third-party tools or in-house scripts). But this solution has many limitations, often making it an ineffective or infeasible option:

  • Impossible to statically predict idle times, especially during work hours.
  • Teams can’t access stopped machines with forceful shutdowns.
  • No optimization of compute, only start/stop actions.

Cloud AutoStopping solves the problems of idle cloud wastage and automated cost savings. Customers can now run non-production workloads on fully-orchestrated spot instances and turn them off whenever idle, saving on cloud costs to the most granular extent possible. It’s a dynamic solution to a pressing customer problem or set of them. In particular, Cloud AutoStopping enables customers to solve for the following use cases:

  • Automatically detect idle times and shut down (on-demand) or terminate (spot) resources.
  • Automatically restart resources whenever there is traffic or usage requests.
  • Stopped/terminated machines are always accessible using the same access patterns that the team is used to – DNS link, SSH, RDP, background tasks.
  • Enable running workloads on fully-orchestrated spot instances without worrying about spot interruptions.

Together, this helps customers achieve savings that are 2-3x that of any static resource scheduler, with none of the access issues. It also significantly reduces the barrier to adoption across an organization.

How AutoStopping Rules can help when I am using Amazon EC2 Reserved Instances (RIs) for non-prod workloads?

Using AutoStopping with either on-demand instances or spot instances will results in 70%+ savings without any long-term commitments or upfront payments. With RIs, you can save up to ~ 60-65% (lower savings) and you have long-term (1-3yrs+) commitments and upfront payments (for highest savings). So it is beneficial to release RIs and use AutoStopping with on-demand or spot.

How spot instance interruptions are handled?

In the event of spot interruption, an alternate spot instance is provisioned. In case there is no alternate spot available we fall back to on-demand and continue to poll for spot capacity. Once a spot capacity is available, we do a reverse fall-back from on-demand to spot.

All this is automated, with no manual intervention.

Azure

How do AutoStopping Rules access the AWS VMs?

The VMs can be accessed using any of the following methods:

  • DNS Link
  • SSH/RDP
Do AutoStopping Rules need an Application Gateway or Azure Web Application Firewall (WAF) for non-prod workloads?

Yes, you need to create an Application Gateway for Azure. Azure Application Gateway is a web traffic load balancer that enables you to manage traffic to your web applications. Application Gateway can make routing decisions based on additional attributes of an HTTP request, for example, URI path or host headers.

For more information, see Create an Application Gateway for Azure.

How AutoStopping Rules can help when I shut down my VMs during non-working hours?

Before Cloud AutoStopping, the only other option to solve these problems was the use of static resource schedulers (third-party tools or in-house scripts). But this solution has many limitations, often making it an ineffective or infeasible option:

  • Impossible to statically predict idle times, especially during work hours.
  • Teams can’t access stopped machines with forceful shutdowns.
  • No optimization of compute, only start/stop actions.

Cloud AutoStopping solves the problems of idle cloud wastage and automated cost savings. Customers can now run non-production workloads on fully-orchestrated spot instances and turn them off whenever idle, saving on cloud costs to the most granular extent possible. It’s a dynamic solution to a pressing customer problem or set of them. In particular, Cloud AutoStopping enables customers to solve for the following use cases:

  • Automatically detect idle times and shut down (on-demand) or terminate (spot) resources.
  • Automatically restart resources whenever there is traffic or usage requests.
  • Stopped/terminated machines are always accessible using the same access patterns that the team is used to – DNS link, SSH, RDP, background tasks.
  • Enable running workloads on fully-orchestrated spot instances without worrying about spot interruptions.

Together, this helps customers achieve savings that are 2-3x that of any static resource scheduler, with none of the access issues. It also significantly reduces the barrier to adoption across an organization.


Please Provide Feedback