# Auto-Scaling for Amazon S3 Access Nodes

Auto-scaling enhances efficiency and performance, especially for large-scale operations, by dynamically deploying access nodes in a region only when required, and then promptly powering off and decommissioning the access nodes after they are used.

## Supported AWS Regions

Auto-scaling is supported for all commercial AWS Regions. Edge locations (such as GovCloud, AWS Outposts, Local Zones, and Wavelength Zones) are not supported.

## How Auto-Scaling Works with Amazon S3

Auto-scaling uses a scaling configuration that creates a server group to manage auto-scaled access nodes, and access nodes are automatically provisioned during S3 backup and restore operations based on workload demands.

## Amazon Machine Images (AMIs) Used for Auto-Scaled Access Nodes

Auto-scaled access nodes are created by cloning a Commvault AMI from AWS Marketplace. Subscribe to the following CIS-hardened AMIs before configuring auto-scaling:

- Commvault Cloud Access Node ARM BYOL: Amazon Linux AWS Graviton (ARM 64-bit)

- Commvault Cloud - Amazon Linux Access Node BYOL: Amazon Linux 2023

Important

To enable auto-provisioning of access nodes, you must log in to the AWS Console, accept the terms, and subscribe to the Commvault AMI before configuring auto-scaling. Starting with Commvault Platform Release 11.42.40, access node AMIs have been updated. Subscribe to the latest AMIs before running backup or restore jobs.

For more information about deploying access nodes from AWS Marketplace, see Deploying Commvault Access Node from AWS Marketplace.

## AWS 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 during scaling configuration configuration. 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

## Where Auto-Scaled Access Nodes Are Created

Auto-scaled access nodes are created in the AWS Regions and Availability Zones that you specify in the scaling configuration. The access nodes are deployed in the same region where your S3 buckets reside to optimize data transfer performance and minimize cross-region data transfer costs.

## Decommissioning of Access Nodes

Auto-scaled access nodes shut down after 5 minutes of idle time. If an access node is shut down when a job request is initiated, the access node is powered on and used. If no activity occurs on that access node after the job completes, the access node is deleted after 30 minutes of inactivity from both Command Center and the AWS portal.

If you manually remove an access node from the server group, it is not deleted from Command Center or the AWS portal. You must add the access node back to the server group and allow the automatic process to delete the access node.

## Log Files

The log files for auto-scaling are at the following location on the CommServe server: Commvault\ContentStore\iDataAgent\JobResults\CV_JobResults\AutoScale

×

Loading...