Prepare the Environment

1. Create both an S3 Interface Endpoint and an EC2 Endpoint within the AWS console.
   
   
2. Modify the regions file to alter which server Veeam Backup & Replication will attempt to connect to for S3 and EC2
   
   
   1. On the Veeam Backup Server, edit C:\Program Files\Veeam\Backup and Replication\Backup\AmazonS3Regions.xml
      
      
   2. Find the Region section which corresponds to the location of your PrivateLink.
      Example:
      

       <Region Id="ap-northeast-1" Name="Asia Pacific (Tokyo)" Type="Global">
      

   3. Within that Region's section find the line <Endpoint Type="s3"> and replace the existing DNS value with the S3 Interface Endpoint DNS created in Step 1.
      Note: For S3 the AWS console will display a DNS value starting with an asterisk. When altering the AmazonS3Regions file replace the asterisk with the word bucket.
      
      Example:
      

      <Endpoint Type="S3">s3-ap-northeast-1.amazonaws.com</Endpoint>
      

      Is changed to:
      

      <Endpoint Type="S3">bucket.vpce-00000000000000000-00000000.s3.ap-northeast-1.vpce.amazonaws.com</Endpoint>
      

   4. If there are multiple lines for <Endpoint Type="S3"> in the Region section you are altering, remove all but the one you changed.
      
      Example:
      

      <Region Id="ap-northeast-1" Name="Asia Pacific (Tokyo)" Type="Global">
      <Endpoint Type="S3">s3-ap-northeast-1.amazonaws.com</Endpoint>
      
                              <Endpoint Type="S3">s3.dualstack.ap-northeast-1.amazonaws.com</Endpoint>
                             
      

   5. Within the same Region section find the line <Endpoint Type="EC2"> and replace the existing DNS value with the EC2 Endpoint DNS created in Step 1.
      
      Example:
      

      <Endpoint Type="EC2">ec2.ap-northeast-1.amazonaws.com</Endpoint>
      

      Is changed to:
      

      <Endpoint Type="EC2">vpce-00000000000000000-00000000.ec2.ap-northeast-1.vpce.amazonaws.com</Endpoint>
      

   6. Save the file.