Appliance setup in AWS

Bhagya Shree Chauhan 21 Reputation points

I need to migrate servers from AWS to Azure, Some servers are in different VPCs which do not talk to each other. If need to setup appliance without enabling peering between VPCs, then in that case do we need to setup appliance in each VPC. I don't want VPCs to be peered

0 comments No comments
Sign in to comment

Answer accepted by question author

AI answer

Yes. A separate Azure Migrate replication appliance is required for each isolated VPC if VPC peering (or other network connectivity) is not enabled between them.

Reasoning based on requirements:

  • The replication appliance must have network line-of-sight to every source AWS VM that it will replicate.
  • Source AWS VMs communicate with the replication appliance over HTTPS 443 (control/orchestration) and TCP 9443 (replication data) inbound.
  • The guidance recommends deploying the replication appliance in the same VPC as the source VMs; if it is in a different VPC, the VPCs must be connected via VPC peering.

Since VPCs in this scenario “do not talk to each other” and peering is explicitly not desired, a single appliance cannot reach VMs across those VPC boundaries. Therefore:

  • Deploy one replication appliance VM (Windows Server 2022) per VPC that contains servers to be migrated.
  • Ensure each appliance meets the hardware/software/networking requirements and can reach Azure over HTTPS 443 outbound.
  • Configure security group rules in each VPC so that the local source VMs can reach their local appliance on ports 443 and 9443.

This way, each isolated VPC has its own appliance handling replication for the VMs inside that VPC, without requiring VPC peering.

References:

AI-generated content may be incorrect. Read our transparency notes for more information.

0 additional answers

Sign in to answer

Your answer