Skip to content

Auto Scaling FAQ

View as Markdown

Which regions is Auto Scaling available in?

Section titled “Which regions is Auto Scaling available in?”

Delhi and Chennai. A scale group, its nodes, and its saved image all belong to the same region and the same project. See Create a scale group.

Why is creating a scale group refused in Delhi?

Section titled “Why is creating a scale group refused in Delhi?”

Accounts created on or after May 15, 2026 need an exemption from E2E to create one there. Meanwhile, you can create the scale group in Chennai, from an image saved there. See Troubleshooting Auto Scaling.

A saved image in the Ready state that was saved from a C3, M3, SDC3, E1, or E1WC node, or from the older C, C2, or M series. For Windows, use an image saved from an E1WC node. See Create a scale group.

No. Select Saved Image leaves out GPU images. For the images a scale group can use, see Which images can a scale group use?

How do I roll out a new version of my application?

Section titled “How do I roll out a new version of my application?”

With a new scale group. A scale group keeps the image it was created from, so save a new image, create a new scale group from it, point your load balancer at the new scale group, and delete the old one. See Point an existing load balancer at another scale group.

No. Make the image start your application instead: set up the node you save the image from so that your application starts at boot, for example as a systemd service, and create the scale group from that image. See Save a node as an image.

Can I add an SSH key when I create a scale group?

Section titled “Can I add an SSH key when I create a scale group?”

No. Scale group nodes already keep the SSH keys and root password saved with the image. Add your key and set the root password on the source node before you save the image. See Sign in to scale group nodes.

Can I change a scale group’s plan, name, or encryption?

Section titled “Can I change a scale group’s plan, name, or encryption?”

No. The saved image, the plan, the name, and the encryption setting are fixed when you create the scale group. To change one, create a new scale group with the settings you want. You can change the rest later: the node counts and the policy while the scale group reads Running, its security groups while it reads Running or Scaling, and its VPCs and public IP while it reads Stopped. See Create a scale group.

Can a scale group scale down to zero nodes?

Section titled “Can a scale group scale down to zero nodes?”

No. Minimum Node is at least 1. To run no nodes while keeping the scale group’s settings, stop the scale group. You then pay nothing for nodes. The saved image and any load balancer or VPC still have their own charges. See Stop the scale group.

Can I remove one particular node from a scale group?

Section titled “Can I remove one particular node from a scale group?”

No. You set how many nodes run, and the scale group chooses which nodes it removes. See Resize the scale group.

Why does the scale group’s node count differ from what I set?

Section titled “Why does the scale group’s node count differ from what I set?”

Because the policies add and remove nodes, while Desired nodes keeps the last count you set, by hand or at creation. Active Node Details lists the nodes running now, and Audit Logs records each scaling step. See Monitor a scale group.

CPU use or a schedule. An elastic policy scales on CPU, and a scheduled policy scales at the times you set, in India Standard Time (IST). Elastic and Scheduled Policy uses both. See Set an elastic policy.

No, not in the portal. The elastic policy scales on CPU. To scale on memory or another measurement, watch it with your own monitoring and set the count with Resize Service. See Set an elastic policy.

No. A scheduled policy has one Upscale Recurrence and one Downscale Recurrence, each with its own number of nodes. To also scale on load, choose Elastic and Scheduled Policy; both policies then work within the same Minimum Node and Maximum Node. See Set a scheduled policy.

Which load balancer can I put in front of a scale group?

Section titled “Which load balancer can I put in front of a scale group?”

An Application Load Balancer (ALB), with Backend Type set to Auto Scale Group. See Put a load balancer in front of a scale group.

Do new nodes join the load balancer by themselves?

Section titled “Do new nodes join the load balancer by themselves?”

Yes. E2E adds each node to the load balancer when it starts running, and takes it off when it is removed. The load balancer sends traffic to each node’s private IP on the Scaler Port. Health Check is on by default. The load balancer skips any node that fails the check: a node passes when it answers a HEAD / request on the Scaler Port with a success status, such as 200 OK. See Put a load balancer in front of a scale group.

Why are my scale group nodes not on the Nodes page?

Section titled “Why are my scale group nodes not on the Nodes page?”

They are listed on the scale group’s own Active Node Details tab. See Monitor a scale group.

Can I turn on encryption for an existing scale group?

Section titled “Can I turn on encryption for an existing scale group?”

No. You can turn on encryption only when you create the scale group, and it stays on for the life of the scale group. To encrypt the nodes, create a new scale group with Enable Encryption on. See Encrypt the nodes.

They depend on the scale group’s status. Stop is available while the scale group reads Running, and Delete while it reads Running, Stopped, Failed, or Failed Deleting. For every state, see the table in Read the scale group’s status. Your role in the current project also needs the update permission for Stop and the delete permission for Delete. See Stop, Start, Delete, or Resize Service is not available.

What do I do when a scale group shows Failed Scaling?

Section titled “What do I do when a scale group shows Failed Scaling?”

Wait, refresh Manage Auto Scaling, and read the latest entry on the scale group’s Audit Logs tab. While the scale group reads Failed Scaling, Resize Service, Stop, Start, and Delete are not available. If it still reads Failed Scaling, contact support. See The scale group shows Failed Scaling.

A scale group has no charge of its own. Each node is billed like any node on its plan, by the minute, from when it starts until it is removed. Scale groups use hourly billing only, with no committed pricing. For current prices, see E2E’s pricing page.

Am I charged while a scale group is stopped?

Section titled “Am I charged while a scale group is stopped?”

No, not for nodes. A stopped scale group has none, so you pay nothing for them. Your saved image, load balancer, VPC, and any other product you use with the scale group are still billed. See Stop the scale group.

Can I delete the saved image a scale group uses?

Section titled “Can I delete the saved image a scale group uses?”

Yes, once no scale group uses it. First delete every scale group built from the image. Deleting a scale group leaves its saved image in place, so you then delete the image yourself. See Delete a scale group.