- External Connections (S2C)
- AWS TGW
- Native Peering
- External CA Certificates
Purpose
The External Connections (Site2Cloud) page configures and manages Site2Cloud connections between Aviatrix Gateways and external devices.Elements

- + External Connection button: Starts the workflow to create a new External Device, AWS Virtual Gateway, Azure Virtual Network Gateway, or Microsoft SSE Solution connection.
- BGP Settings button: Configures BGP settings to receive notifications on overlapping BGP address and route limitations, and to set the maximum BGP AS path length.
- External Connections (S2C) table: Displays the list of existing S2C connections and their details.
- Delete button: Removes an existing S2C connection from the table.
- Actions button: Download configuration files, connectivity Diagnostics, and BGP Diagnostics for an S2C connection.
Actions
Create External Connection
Create External Connection
To create an external Site2Cloud connection:
- Go to Networking > Connectivity > External Connections (S2C).
- Click + External Connection.
- Select the connection type (External Device, AWS Virtual Gateway, Azure Virtual Network Gateway, or Microsoft SSE Solution).
- Configure the connection parameters (Name, Tunnel Type, Local Gateway, Remote Device IP, subnets, and BGP settings as applicable).
- Click Save.
Parameter Details
| Sl. No. | CoPilot Parameter Name | Description |
|---|---|---|
| 1 | Name | Name of the external connection. |
| 2 | Tunnel Type | Type of tunnel used for the connection, for example BGP over IPsec. |
| 3 | Local Gateway | Name of the Aviatrix Gateway that initiates the connection. |
| 4 | Local Gateway IP | Public IP address of the local gateway. |
| 5 | Gateway Interface | Network interface on the local gateway used for the tunnel. |
| 6 | Remote Device IP | Public IP address of the remote device. |
| 7 | Local Subnet | Subnet or tag advertised from the local side. |
| 8 | Remote Subnet | Subnet or tag advertised from the remote side. |
| 9 | Local ASN | Autonomous system number used by the local gateway. |
| 10 | Remote ASN | Autonomous system number used by the remote device. |
| 11 | BGP Local IP | Local IP address used for the BGP session. |
| 12 | BGP Neighbor IP | Remote IP address used for the BGP session. |
| 13 | BGP Neighbor Status | Current status of the BGP session. |
| 14 | BFD Status | Status of Bidirectional Forwarding Detection for the connection. |
Configure BGP Settings
Configure BGP Settings
To configure BGP settings for Site2Cloud connections:
- Go to Networking > Connectivity > External Connections (S2C).
- Click BGP Settings.
- Configure notifications for overlapping BGP address and route limitations.
- Set the maximum BGP AS path length.
- Save your changes.
Delete External Connection
Delete External Connection
To delete an external Site2Cloud connection:
- Go to Networking > Connectivity > External Connections (S2C).
- Locate the connection in the External Connections (S2C) table.
- Click the Delete button for the connection.
- Confirm the deletion.
Download Configuration or Run Diagnostics
Download Configuration or Run Diagnostics
To download configuration files or run diagnostics for an S2C connection:
- Go to Networking > Connectivity > External Connections (S2C).
- Locate the connection in the External Connections (S2C) table.
- Click the Actions button for the connection.
- Select Download configuration files, Connectivity Diagnostics, or BGP Diagnostics as needed.
BGP over LAN: In AWS, BGP over LAN allows BGP-enabled Spoke Gateways to connect to third-party instances in the same VPC without IPsec or GRE. In Azure, it allows connection to third-party instances in the same VNet. Each connection can connect to one or at most two third-party instances. BGP over LAN is not supported for GCP, OCI, and Alibaba Cloud. For Azure, you must indicate the number of LAN interfaces (maximum eight). Adding new LAN interfaces to an Azure Spoke Gateway reboots the gateway and may cause traffic disruption. You cannot delete an interface after the Spoke Gateway is created.


