Configuring Private Networks for Production Accounts

If you have multiple AWS accounts and want to deploy worker instances in production accounts, the estimated cost of VPC endpoints per account may occur to be significantly high. To reduce the cost, you can create a single resource share in one AWS account for all subnets to which the worker instances will be connected, and share the resource with other AWS accounts belonging to the same organization.

For Veeam Backup for AWS to be able to deploy worker instances in a private environment in production accounts, perform the following steps:

  1. Create VPC interface and S3 interface endpoints for subnets to which the worker instances will be connected.
  2. Create a peering connection between VPCs.
  3. Add routes to the route tables associated with the subnets of the VPCs.
  1. Create a resource share to share the subnets with other AWS accounts.
  1. In each production account, create security groups that will be associated with worker instances connected to the shared subnets.

Private Networks

Page updated 5/31/2024

Page content applies to build 8.1.0.7