Add an interface with an associated route table on a cloud Airwall Gateway

If you need to attach a route table to an interface you’re adding in AWS or Azure, you’ll need to add the interface and attach the route table before you reboot the Airwall Gateway.

Supported versions

v3.0.0 Conductors
AWS and Azure Cloud Airwall Gateways

Supported Roles: AWS or Azure cloud administrator, and Conductor system administrator , or network administrator with permissions to create cloud Airwall Gateways

CAUTION: If you reboot the Airwall Gateway before you’ve associated the route table, the Conductor sees the new interface and checks the route table. When it doesn’t find a specific one, it tries to find one, and it may not find the correct one. It doesn’t recheck the route table once it’s found one.

For the most up-to-date information, see the documentation for your respective cloud provider.

If you’ve already rebooted, see Get an AWS Airwall Gateway to pull the correct route table.

Associate the route table to your new interface (for example, Port 3) subnet.
Create a new interface (for example, Port 3).
Attach the new interface to the Airwall Gateway.
Reboot the Airwall Gateway.

Here are some suggested resources for AWS and Azure documentation on multiple NICs:

AWS:

Associate a protected subnet with a protected route table first: https://docs.aws.amazon.com/vpc/latest/userguide/WorkWithRouteTables.html#AssociateSubnet
Attach an interface to an instance: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html#working-with-enis

Azure:

Associate a protected subnet with a protected route table first: https://docs.microsoft.com/en-us/azure/virtual-network/manage-route-table#associate-a-route-table-to-a-subnet

Attach an interface to an instance: https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface-vm