Launch Aviatrix Spoke Gateways

In this blog, I’ve logged steps to provision AWS VPC or Azure vNet for launching Aviatrix Spoke Gateways (HPE and none-HPE)

AWS – HPE

Create VPC with CIDR allocated for application.
Create subnets to populate application CIDR range.
Create IGW and associate with VPC.
For application subnets, whether they are public or private, create one dedicated route table per subnet.
For application public subnet route table, associate 0.0.0.0 with IGW.
On VPC, add /25 CIDR for Aviatrix HPE spoke gateways. (Each HPE gateway require /26 for up to 50 secondary IPs)
In Aviatrix Controller -> Multi-cloud Transit -> Setup -> Spoke -> Select VPC and enable High Performance Encryption, select the first /26 within added /25 range, and launch spoke gateway
In Aviatrix Controller -> Multi-cloud Transit -> Setup -> Spoke -> Enable/Disable HA to an Aviatrix Spoke Gateway -> Select primary gateway, select the second /26 range and AZ, click Enable

Create VPC with CIDR allocated for application.
Create subnets to populate application CIDR range.
Create IGW and associate with VPC.
For application subnets, whether they are public or private, create one dedicated route table per subnet.
For application public subnet route table, associate 0.0.0.0 with IGW.
On VPC, add /27 CIDR for Aviatrix none HPE spoke gateways.
Within /27 range, create two /28 subnets in different AZ, one for primary spoke gateway, one for HA spoke gateway.
Create route table for each spoke gateway subnet, and associate 0.0.0.0 with IGW
Associate each route table to corresponding subnet
In Aviatrix Controller -> Multi-cloud Transit -> Setup -> Spoke -> Select VPC, select the first /28 subnet, and launch spoke gateway
In Aviatrix Controller -> Multi-cloud Transit -> Setup -> Spoke -> Enable/Disable HA to an Aviatrix Spoke Gateway -> Select primary gateway, select the second /28 subnet, click Enable

Create vNet with CIDR allocated for application.
Create subnets to populate application CIDR range.
For application subnets, whether they are public or private, create one dedicated route table per subnet.
For application public subnet route table, associate 0.0.0.0 with internet.
For application private subnet route table, associate 0.0.0.0 with none.
Associate each route table to corresponding subnet
On vNet address space, add /25 CIDR for Aviatrix HPE spoke gateways. (Each HPE gateway require /26 for up to 50 secondary IPs)
In Aviatrix Controller -> Multi-cloud Transit -> Setup -> Spoke -> Select vNet and enable High Performance Encryption, select the first /26 within added /25 range, and launch spoke gateway
In Aviatrix Controller -> Multi-cloud Transit -> Setup -> Spoke -> Enable/Disable HA to an Aviatrix Spoke Gateway -> Select primary gateway, select the second /26 range and AZ, click Enable

Create vNet with CIDR allocated for application.
Create subnets to populate application CIDR range.
For application subnets, whether they are public or private, create one dedicated route table per subnet.
For application public subnet route table, associate 0.0.0.0 with internet.
For application private subnet route table, associate 0.0.0.0 with none.
On vNet address space, add /27 CIDR for Aviatrix HPE spoke gateways.
Within /27 range, create two /28 subnets in different AZ, one for primary spoke gateway, one for HA spoke gateway.
For each spoke gateway subnet, create a route table, and add 0.0.0.0 target Internet
Associate each route table to corresponding subnet
In Aviatrix Controller -> Multi-cloud Transit -> Setup -> Spoke -> Select vNet and disable High Performance Encryption, select the first /28 subnet with appropriate AZ, and launch spoke gateway
In Aviatrix Controller -> Multi-cloud Transit -> Setup -> Spoke -> Enable/Disable HA to an Aviatrix Spoke Gateway -> Select primary gateway, select the second /28 subnet with appropriate AZ, click Enable