How to Connect to an Object Storage Repository via AWS Privatelink / Direct Connect

Prepare the AWS Environment

1. ^{(If using AWS Direct Connect, skip to step 2.)} 
   For AWS PrivateLink, configure a VPN connection to the VPC where you plan to deploy the PrivateLink Endpoint. One of the ways to do this is to create a tunnel on the VM gateway using AWS Client VPN.
   
2. Create Endpoints in VPC:
   1. Create an S3 Interface Endpoint in your VPC. It will be assigned a DNS name that you can see in the AWS Console under VPC - Endpoints when selecting the corresponding Endpoint.
   2. An EC2 Endpoint must also be created if intending to use Archive Tier.

Prepare the Veeam Backup & Replication Environment

3. Disable automatic updating of the AmazonS3Regions.xml file by creating the following registry value on the Veeam Backup Server.
   ^{This will prevent Veeam Backup & Replication from overwriting the changes you'll make in the next section of this guide.}
   
   Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
   Value Name: CloudRegionsDisableUpdate
   Value Type: DWORD (32-Bit) Value
   Value Data: 1
4. Disable certificate revocation checks by creating the following setting on the machine that is assigned as the Gateway server within the Object Storage Repository settings:
   • For Windows-based Gateway servers, create the following registry value:
     
     Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
     Value Name: ObjectStorageTlsRevocationCheck
     Value Type: DWORD (32-Bit) Value
     Value Data: 0
     
   • For Linux-based Gateway servers, add the following entry to the /etc/VeeamAgentConfigIf the /etc/VeeamAgentConfig file is not present, it must be created. file:
     

     ObjectStorageTlsRevocationCheck=0
     

   Note: Prior to Veeam Backup & Replication 12, this setting was named S3TLSRevocationCheck.
5. To configure the Helper Appliance used for Object Storage Repository Health Checks to use the private IP address, add the following registry value on the Veeam Backup Server:
   
   Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication
   Value Name: ArchiveUsePrivateIpForAmazonHelperAppliance
   Value Type: DWORD (32-Bit) Value
   Value Data: 1
   
   1 = Enable Archive Appliance use Private IP | 0 = Disable (Default)
6. If you plan to use Amazon Glacier for Archive Tier, review the following:
   • Certificate revocation checks must be permitted. The Veeam Backup Server and the VPC where the Archiver Appliance is deployed must have access to certificate revocation lists used by AWS over port 80 (*.amazontrust.com).
   • The following additional registry values must be created on the Veeam Backup Server:
     • Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
       Value Name: ArchiveFreezingUsePrivateIpForAmazonAppliance
       Value Type: DWORD (32-Bit) Value
       Value Data: 1
     • Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
       Value Name: ArchiveFreezingSkipProxyValidation
       Value Type: DWORD (32-Bit) Value
       Value Data: 1

Add Object Storage Repository

Now that the AmazonS3Regions.xml file has been modified, when you select the entry you changed within Veeam Backup & Replication, the software will connect to the specified endpoints.

• For Object Storage Repository, Add Amazon S3 Storage repository. On the Bucket tab of the wizard, select the Region that matches the Region name you modified in the AmazonS3Regions.xml file.
• For Capacity Tier, Add Amazon S3 Storage repository. On the Bucket tab of the wizard, select the Region that matches the Region name you modified in the AmazonS3Regions.xml file. Then add Capacity Tier to Scale-Out Backup Repository
• For Archive Tier, Add Amazon S3 Glacier Storage repository. On the Bucket tab of the wizard, select the Data center that matches the Region name you modified in the AmazonS3Regions.xml file. Then, add Archive Tier to the Scale-Out Backup Repository.