Skip to main content

Topology - Multiple VPC

Architecture​

Use this topology when your workload must span multiple VPCs, and even multiple AWS Accounts.

In this topology, Combine is deployed to each VPC in your workload. Route 53 private DNS entries redirect all emulated endpoint traffic to the local Endpoint Servers.

Architecture Diagram​

Multiple VPC Architecture

NOTE: This diagram is for Combine AWS, but from a networking perspective it is analogous to Combine Azure.

Advantages​

  • This architecture is simple and predictable.
  • Each AWS Account can be configured independently.

Disadvantages​

  • At present, User Management can be performed only in a single designated AWS Account. Combine calls this account the "User Management Account" and calls the other AWS Accounts "Follower Accounts". (See Add Follower Account.)
  • At present, the Alert Events for an AWS Account are displayed only on the TAP Dashboard of that AWS Account. We are designing a new architecture for the TAP Dashboard with the capability for multiple accounts and multiple tenants.
  • AWS spend is higher because additional infrastructure is deployed to each VPC.

Shared Responsibilities​

  • None.
Last updated on by Stephen Mouring