Configure private connectivity for Air Gap Protect storage

Use AWS PrivateLink to enable private connectivity between your environment and an Amazon S3 bucket used for Air Gap Protect.

Requirements and considerations

Network connectivity

• Your on-premises environment must be connected to AWS using Direct Connect.

• The connection must support expected backup and restore throughput.

• Routing must allow access to the VPC where the interface endpoint is deployed.

DNS configuration

• Configure DNS so that Amazon S3 endpoints resolve to the private IP address of the interface VPC endpoint.

• Verify that $[bucketname].s3.$[region].amazonaws.com resolves using your private DNS configuration.

VPC endpoint configuration

• Create an interface VPC endpoint for the S3 service (com.amazonaws.$[region].s3).

• The endpoint must:

  • Be associated with subnets reachable from your on-premises network

  • Have private DNS enabled

• The security group associated with the endpoint must allow inbound HTTPS (port 443) traffic from your on-premises network.

Access and permissions

• The S3 bucket and access point must allow access from:

  • Your AWS account

  • The Commvault-managed account used by Commvault

• Do not restrict access only to service principals within your AWS account.

Cross-account considerations

• Air Gap Protect uses a cross-account access model.

• You must provide your AWS account ID and, optionally, VPC endpoint IDs to Commvault.

Cost considerations

AWS may charge for:

• Interface VPC endpoint usage

• Data processing through PrivateLink

• Data transfer through Direct Connect

Create an interface VPC endpoint

1. Log on to the AWS Management Console with permissions to manage VPC endpoints.

2. In the target VPC, create an interface endpoint for the S3 service (com.amazonaws.$[region].s3).

3. Associate the endpoint with the required subnets and security groups.

4. Enable private DNS.

5. Create the endpoint.

Provide account information to Commvault

1. Log on to https://support.commvault.com and create a support request that includes:

   • AWS account ID

   • VPC endpoint IDs (optional, if you want to restrict access)

Validate connectivity

After Commvault confirms configuration:

1. Launch an EC2 instance in the VPC that contains the interface endpoint.

2. Verify DNS resolution by validating that the S3 endpoint resolves to a private IP address.

3. Access the S3 bucket using the access point.

4. Confirm the following:

   • Data transfer succeeds (read and write operations)

   • Traffic flows through the VPC endpoint

   • No traffic routes through the public internet

Use Azure Private Link to enable private connectivity between your environment and an Azure Blob Storage account used for Air Gap Protect.

Requirements and considerations

Network connectivity

• Your on-premises environment must be connected to Azure using ExpressRoute.

• The connection must support expected workload performance.

DNS configuration

• Configure DNS so that the storage account endpoint resolves to the private endpoint IP address.

• If you use custom DNS servers, configure forwarding for Azure private link zones.

Private endpoint configuration

• The private endpoint must be deployed in a subnet reachable from your on-premises network.

• The subnet must allow private endpoint deployment.

Access and permissions

• You must have permissions to create private endpoints and manage network configuration.

• Storage account access must allow connections through the private endpoint.

Network policies

For the subnet hosting the private endpoint, disable:

• privateLinkServiceNetworkPolicies

• privateEndpointNetworkPolicies

Create a private endpoint

To create a private endpoint:

1. Log on to https://support.commvault.com and request a storage resource ID.

2. In Azure, create a private endpoint using the storage resource ID.

   For information about creating a private endpoint, see Azure documentation.

Request endpoint approval

1. Contact Commvault Support.

2. Provide the name of the private endpoint.

3. Wait for approval confirmation.

Configure DNS

1. To identify the storage account name, go to Manage > Air Gap Protect and select the storage.

2. Update your DNS server to resolve the storage account endpoint to the private endpoint IP address.

Validate connectivity

1. From a VM in your network, verify DNS resolution.

   The storage account endpoint resolves to a private IP address.

2. Access the storage account.

3. Confirm:

   • Data transfer succeeds.

   • Traffic flows through the private endpoint.

Azure ExpressRoute is supported by default in Commvault.

If your environment already uses ExpressRoute:

• No additional configuration is required in Commvault.

• Verify that DNS and routing are correctly configured for private access to storage endpoints.

Use Google Cloud Private Service Connect (PSC) to enable private connectivity between your environment and a Google Cloud Storage bucket used for Air Gap Protect.

Supported configuration

• Google Cloud Storage accessed through Google Cloud Private Service Connect

• DNS resolution through private DNS services

• Environments that use VPC Service Controls

Requirements and considerations

To use Google Cloud Private Service Connect (PSC) with Air Gap Protect:

• Create a PSC endpoint for Google APIs.

• Configure DNS so that Google Cloud Storage traffic resolves through the PSC endpoint.

• Validate connectivity from resources in your VPC.

• Verify that the service accounts that access the bucket have the required Google Cloud Storage permissions.

For detailed PSC deployment instructions, see the Google Cloud documentation.

Provide account information to Commvault

After you configure private connectivity, log on to support.commvault.com and provide the following information in a support request:

Information	Purpose
Consumer project ID	Used to grant access to Google Cloud Storage resources
Service account email addresses	Used to assign the required permissions
VPC Service Controls perimeter information, if applicable	Used when access must be restricted through VPC Service Controls