API (Self-hosted on AWS): Network topology

We provide three fulfillment options for different networking needs.

Dedicated public VPC (#)

Deploy attachmentAV into a pre-configured VPC. The ALB and the EC2 instances are running in public subnets for minimal networking costs. Of course, security groups are used to control incoming traffic.

attachmentAV - Dedicated public VPC

Dedicated private VPC (#)

Deploy attachmentAV into a pre-configured VPC. The ALB and the EC2 instances are running in private subnets for maximum security and compliance.

The VpcCidrBlock configuration parameter must not overlap with any of your existing VPCs to allow VPC peering!

To connect to attachmentAV, you have to peer your VPC with the attachmentAV VPC.

attachmentAV - Dedicated private VPC

Existing VPC (#)

Deploy attachmentAV into an existing VPC. Choose whether you want to place the ALB and the EC2 instances in public or private subnets.

attachmentAV - Existing VPC

Please follow the Existing VPC Network Guide.

Need more help?

Write us, and we'll get back to you as soon as we can.

Send us an email