Auto-scaling enables dynamic scaling of access nodes to meet changing workload demands. Based on a defined scaling configuration, the system automatically deploys access nodes within a region only when required and decommissions them once operations are complete. This ensures optimal performance while minimizing unnecessary resource consumption.
Auto-scaling is particularly critical during large-scale backup, restore, and disaster recovery operations, where data volumes and workload demands can vary significantly. By allocating access nodes on demand and powering them down when no longer needed, the system prevents bottlenecks, reduces operational overhead, and optimizes compute costs.
Auto-scaling can be used for the following operations:
-
Backup and restore
-
File indexing
-
Replication
-
Threat Scan
For information about auto-scaling for all Virtualization workloads, see Auto-Scaling for Virtualization Access Nodes.
Amazon EC2 instance types used for auto-scaled access nodes
By default, an AWS Graviton (Arm-based, 64-bit) image with the c7g.xlarge instance type is used to create the auto-scaled access nodes. If an AWS Graviton (Arm-based, 64-bit) image is not available in the AWS Region, then an x86 image with a c6a.xlarge instance is used.
You can specify a different instance type. The following AWS instance types are supported:
-
AWS Graviton (Arm-based, 64-bit): c7g.xlarge (default), c6g.large, c6g.xlarge, c6g.2xlarge, r6g.large, r6g.xlarge, r6g.2xlarge, r6g.4xlarge
-
x86: c6a.xlarge (default), c5.large, c5.xlarge, c5.2xlarge, m5a.2xlarge, r5a.large, r5a.xlarge
Deployment location of auto-scaled access nodes
The access nodes are created in zones or regions, depending on which transport mode is used:
-
EBS direct transport mode: In regions
-
AWS VM Import/Export transport mode: In regions
-
HotAdd transport mode: In zones