> For the complete documentation index, see [llms.txt](https://docs.acecloud.ai/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acecloud.ai/knowledge-base/compute/how-to-manage-autoscaling-deployments.md).

# How to Manage Autoscaling Deployments?

### **a. How to view the list of all Autoscaling Deployments?**

To view a list of all autoscaling deployments, follow the steps given below:

**Step 1:** [Login](https://customer.acecloudhosting.com/index.php?m=ace_product_register_addon\&action=login) to your account.

**Step 2:** Navigate to **Compute,** then **Autoscaling,** and then click on **Deployments**. Here, you can view all your deployments.

<figure><img src="/files/Iyaxnfnu2KzCzHY8XGc5" alt=""><figcaption></figcaption></figure>

### **b. How to create an Autoscaling Deployment?**

To create an autoscaling deployment, follow the steps given below:

**Step 1:** Click on the **Create Deployment** button.

<figure><img src="/files/FRaOmpLITDOovlcp31AY" alt=""><figcaption></figcaption></figure>

**Step 2:** Enter the **Deployment Details.**

<figure><img src="/files/VmSr2i6vfIypEiz6s3PN" alt=""><figcaption></figcaption></figure>

| **Field**            | **Description**                                                                 |
| -------------------- | ------------------------------------------------------------------------------- |
| **Deployment Name**  | Enter the name you want to keep for the autoscaling deployment.                 |
| **Select Template**  | Select the template you want to attach in the autoscaling deployment.           |
| **Template Version** | Select which version of the chosen Template should be used for this Deployment. |

**Step 3:** Enter **Scaling and Deployment specifications**.

<figure><img src="/files/WlGHqN86EAqUeyTLkMcT" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="276.5"></th><th></th></tr></thead><tbody><tr><td><strong>Field</strong></td><td><strong>Description</strong></td></tr><tr><td><strong>Scaling Parameter</strong></td><td>Select the parameter from CPU or RAM for scaling up/down according to their usage.</td></tr><tr><td><strong>Min Threshold (in 30% - 90%)</strong></td><td>Enter the utilization percentage to scale down the autoscaling deployment for the parameter you selected above.<br><strong>Note:</strong> The utilization percentage should be in the range of (30% - 90%)</td></tr><tr><td><strong>Max Threshold</strong> <strong>(in 40% - 95%)</strong></td><td><p>Enter the utilization percentage to scale up the autoscaling deployment for the parameter you selected above.</p><p><strong>Note:</strong> The utilization percentage should be in the range of (40% - 95%)</p></td></tr><tr><td><strong>Cool Down Time (min 60 sec.)</strong></td><td>Enter the time in seconds; this is the time period where scaling up/down is restricted, just after the node was scaled up/down.</td></tr><tr><td><strong>Capacity Unit</strong></td><td>The unit used for measuring deployment capacity. Currently, capacity is measured in nodes.</td></tr><tr><td><strong>Max Capacity (Max. 30)</strong></td><td>Enter the number of nodes that can be added at max while scaling up the deployment.<br><strong>Note:</strong> You cannot add more than 30 nodes.</td></tr><tr><td><strong>Desired Capacity</strong></td><td>Enter the desired number of nodes for the deployment. This value must be less than or equal to the max capacity.</td></tr><tr><td><strong>Nodes Scale Count (Max. 30)</strong></td><td><p>Enter the number of nodes that you want to add/remove while you scale up/down the autoscaling deployment.<br><strong>Note:</strong> </p><p><strong>a.</strong> You cannot add more than 30 nodes.</p><p><strong>b.</strong> You should also have the quota required for scaling up the deployment.</p></td></tr></tbody></table>

**Step 4:** Load Balancer Configuration

**In the Load Balancer Details section, configure the load balancer settings for your autoscaling deployment.**
\\

\
1\. Toggle **Integrate with Load Balancer** to **Yes** to enable load balancer integration for the deployment.
\
2\. Choose whether to use an existing load balancer:

* **Yes** – Select an existing load balancer.
* **No** – Create a new load balancer and configure its settings.

3. Select the Load Balancer Type:

* **Application Load Balancer (ALB)** – Recommended for HTTP and HTTPS traffic. Provides advanced routing and application-level traffic management.
* **Network Load Balancer (NLB)** – Suitable for high-performance workloads, TLS offloading, UDP traffic, and static IP requirements.

4. Enter a unique **Load Balancer Name**.
5. Enable **Assign Public IP** if the load balancer needs to be accessible from the internet.

<figure><img src="/files/Oef7ELGVBQcs5hlEFN7t" alt=""><figcaption></figcaption></figure>

**Listener Configuration**
\\

A listener checks for incoming client connection requests and forwards traffic to the appropriate backend pool.

1. Under **Listener Configuration**, click **Add Listener** if you want to configure multiple listeners.
2. Provide the following details:

* **Name** – Enter a name for the listener.
* **Protocol** – Select the listener protocol (for example, HTTP, HTTPS, TCP, or UDP).
* **Port** – Specify the port on which the listener will accept traffic.

**Pool Configuration**
\\

A pool defines the group of backend instances that receive traffic from the listener.
\\

1. Under **Pool Configuration**, click **Add Pool** to create additional backend pools if required.
2. Configure the following settings:

* **Protocol** – Select the protocol used for communication with backend instances.
* **Port** – Enter the backend service port.
* **Algorithm** – Select the load-balancing algorithm used to distribute traffic among instances.

**Health Monitor Configuration**
\\

Health monitors periodically check the availability of backend instances and ensure traffic is routed only to healthy resources.
\\

1. Toggle **Enable Health Monitor** to **Yes**.
2. Under **Health Monitor Configuration**, click **Add Health Monitor** if you need multiple health checks.
3. Configure the following settings:

* **Protocol** – Select the protocol used for health checks.
* **URL Path** – Specify the endpoint to be monitored (for example, / or /health).
* **HTTP Method** – Select the HTTP method used for health checks.

<figure><img src="/files/1e7GxwrTMbbK4SSKtM2p" alt=""><figcaption></figcaption></figure>

**Step 5: Additional Properties**

**Configure notification settings for the autoscaling deployment.**

1. Under **Notification Type**, select the preferred notification method. Currently, **Email** is supported.
2. In the **User Email** field, enter the email address(es) that should receive deployment notifications.

* To add multiple email addresses, separate them with commas.
* Ensure that all entered email addresses are valid.

These email addresses will receive notifications related to the autoscaling deployment and its associated events.

**Step 6:** Review the deployment details and click on the **Create Deployment** button.

<figure><img src="/files/lKRKNFnQsvEi0VDmlpIH" alt=""><figcaption></figcaption></figure>

### **c. How to delete an Autoscaling Deployment?**

To delete an autoscaling deployment, follow the steps given below:

**Step 1:** Choose the deployment you want to delete, click on **Actions**, and select **Delete Deployment** from the drop-down menu.

<figure><img src="/files/0LNqlyT8GgjID6SRHYOk" alt=""><figcaption></figcaption></figure>

**Step 2:** Click on **Delete** to confirm the deletion.

<figure><img src="/files/hHH87LEHJ3RHMfxN0V7Q" alt=""><figcaption></figcaption></figure>

### &#x20;&#x64;**. How to view Autoscaling Deployment Overview?**

To view an autoscaling deployment overview, follow the steps given below:

**Step 1:** Choose the deployment for which you want to view the overview, then click **Deployment Name.**

<figure><img src="/files/dwZIJAyGQGJ0MCUiZLvT" alt=""><figcaption></figcaption></figure>

**Step 2:** Here, you can view the deployment overview.

<figure><img src="/files/YPTGGWX0jVI5lQc8a1Sg" alt=""><figcaption></figcaption></figure>