Creating a Spoke Gateway

Follow the steps below to create a Spoke Gateway and highly available (HA) Spoke gateway instances.

  1. In Aviatrix CoPilot, go to Cloud Fabric > Gateways > Spoke Gateways tab.

    For quick access, at the top of the navigation panel, type Spoke Gateways in the search bar.
  2. To create a Spoke Gateway, click + Spoke Gateway and provide the following information.




    A name for the Spoke Gateway.


    The Cloud Service Provider (CSP) where to create the Spoke Gateway.

    For AWS and Azure, you can use the dropdown menu to select Standard or Global, China, or GovCloud.


    The cloud access account for creating the Spoke Gateway.


    The cloud region in which to create the Spoke Gateway.


    The VPC or VNet in the selected region in which to create the Spoke Gateway.

    Instance Size

    The gateway instance size.

    When selecting the gateway size, note that the size you select affects your IPsec performance.

    High Performance Encryption

    To enable High Performance Encryption (HPE) for the Spoke Gateway, set this toggle to On.

    HPE enables 10Gbps and higher IPsec performance between two single Aviatrix Gateway instances or between a single Aviatrix Gateway instance and on-prem Aviatrix appliance.

    You cannot turn High Performance Encryption On or Off after the Spoke Gateway is created.

    Attach to Transit Gateway

    Select the Transit Gateway to attach to the Spoke Gateway.

    Attach to Egress Transit FireNet

    Select the Egress Transit FireNet to attach to the Spoke Gateway.

    This option is only available if an Egress Transit FireNet has been created.

    In the Advanced Settings section, set the advanced gateway settings that may apply.



    BGP (all clouds)

    To enable the Spoke Gateway to run BGP connection to external routers and dynamically exchange routes, set this toggle to On.

    BGP over LAN (Azure)

    To enable BGP connection over LAN:

    1. Set this toggle to On.

      You must set both BGP and BGP over LAN settings to On to enable BGP over LAN connection on the Spoke Gateway.
    2. Enter the number of LAN interfaces you need (maximum is eight) for the BGP connection.

      You cannot delete an interface after the Transit Gateway is created.

    Global VPC (GCP)

    To connect the Spoke Gateway to a global VPC, set this toggle to On.

    In the Instances section, assign the subnet and IP address for the Spoke Gateway.

    Parameter Description

    Attach to Subnet

    The subnet in which to create the Spoke gateway instance.

    For best practice, select a different subnet in a different availability zone from the other Spoke gateway instances.

    Public IP

    The public IP address of the gateway instance.

    (AWS only) To allocate a new EIP, leave Public IP as Allocate New Static Public IP.

    To create a highly available (HA) gateway instance, click + Instance and designate the subnet and IP address of the gateway instance.

    • A Spoke Gateway can have up to 15 highly available gateway instances.

    • All gateway instances share the same properties as the Spoke Gateway.

    • All gateway instances are created in active-active mode.

    • A BGP-enabled Spoke Gateway can have only two highly available gateway instances.

    • A Spoke Gateway with Site2Cloud, SNAT, DNAT, or FQDN enabled (see here for details on how FQDN gateways are created in CoPilot) can have only two highly available gateway instances.

  3. Click Save.

    You can monitor the progress of the gateway creation by going to CoPilot > Monitor > Notifications > Tasks tab. Click the expand arrow next to the gateway name to see the progress.