Autoscaling
Autoscaling adjusts VM capacity based on workload demand. It helps applications keep enough compute capacity during peak traffic while reducing active resources during quieter periods.
SITE Cloud Autoscaling runs within the Kingdom and keeps scaling logic and data management inside the sovereign cloud environment.
Key Features and Benefits
| Capability | Benefit |
|---|---|
| Adds or removes VM nodes based on operational metrics | Helps reduce latency and timeouts during traffic spikes. |
| Scales down when demand is low | Reduces operational expenditure. |
| Pay for active resources | Improves resource efficiency and ROI. |
| Maintains application availability during unexpected load | Helps applications remain resilient during demand surges. |
| Runs within the SITE Cloud sovereign environment | Supports regional data residency and governance requirements for Riyadh and Jeddah. |
How Autoscaling Groups Work
The core resource is an Autoscaling Group (ASG).
An ASG is a group of VMs managed as a single logical unit. When you define an ASG, you set the boundaries and operational triggers that determine when VMs are added or removed (i.e., scaling-out and scaling-in).
SITE Cloud autoscaling uses a warm pool strategy.
Autoscaling Warm Pools
Warm pools keep instances in a pre-initialized state instead of fully terminating them.
This reduces the delay normally caused by boot time and initialization. When demand increases, instances from the warm pool can move into service more quickly.
Why warm pools matter
Warm pools are intended to improve response time during scaling events while still helping optimize cost during lower-demand periods.
Configuration Parameters
When creating an Autoscaling Group, configure these mandatory parameters:
| Parameter | Description |
|---|---|
| Name and description | A unique name and a description of the application or function supported by the ASG. |
| Minimum node count | The smallest number of running VMs the ASG must maintain. |
| Maximum node count | The highest number of VMs the ASG can scale up to. |
| CPU utilization threshold | Adds a VM when average CPU usage exceeds the threshold for the defined period, and removes a VM when average CPU usage drops below the threshold. |
| Memory utilization threshold | Adds a VM when average memory usage exceeds the threshold for the defined period, and removes a VM when average memory usage drops below the threshold. |
Scaling boundaries
Minimum and maximum node counts act as availability and resource-control boundaries for the Autoscaling Group.
Managing VM Membership
Autoscaling supports these VM membership actions:
| Action | Behavior |
|---|---|
| Add existing VMs | Attach currently running, configured VMs to a new or existing Autoscaling Group. |
| Remove VMs | Detach VMs from the Autoscaling Group. Detached VMs are not terminated; they become standard standalone instances under direct management. |