Operational Defect Database
BugZero found this defect 946 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb4226
How to Connect to an Object Storage Repository via AWS Privatelink / Direct Connect
Last update date:
3/26/2024
Affected products:
Veeam Backup & Replication
Affected releases:
12.1
Fixed releases:
No fixed releases provided.
Description:
Purpose
"This article documents the configuration of Veeam Backup & Replication for using AWS PrivateLink or AWS Direct Connect. These services enable Scale-Out Backup Repository offload to Capacity Tier or Archive Tier, as well as the connection to an Object Storage Repository, without the use of public endpoints. The instructions are applicable to Veeam Backup & Replication version 12 or newer.
Solution
Prepare the AWS Environment (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. Create Endpoints in VPC: 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. An EC2 Endpoint must also be created if intending to use Archive Tier.
More Information
Related Articles: How to use "Restore to Amazon EC2" via AWS PrivateLink / Direct Connect
