Loading...
Loading...
This article documents the configuration of Veeam Backup & Replication for using AWS PrivateLink or AWS Direct Connect. These services enable the following connections without the use of public endpoints: Scale-Out Backup Repository offload to Capacity Tier or Archive Tier Backup to an Object Storage Repository Backup to Veeam Data Cloud Vault (AWS edition)
Prepare the AWS Environment Note: Customers using Veeam Data Cloud Vault (AWS edition) must have their own AWS account, where they will configure the S3 Interface Endpoint through which Veeam Backup & Replication will route S3 traffic. They must also ensure that the AWS region of the S3 Interface Endpoint matches the AWS region used by their VDC Vault. (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 way 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. If you intend to use the Scale-Out Backup Repository Archive Tier, an EC2 Endpoint must also be created.
Related Articles: How to use "Restore to Amazon EC2" via AWS PrivateLink / Direct Connect
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.