> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aviatrix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Network Resiliency Best Practices Guide

> The Network Resiliency Best Practices Guide describes existing Aviatrix features that help you improve the reliability and resiliency of your Aviatrix network. These best practices mean that you will be able to absorb the impact of any issues that occur, while continuing to provide service.

## Overview

The Network Resiliency Best Practices Guide describes existing Aviatrix features
that help you improve the reliability and resiliency of your Aviatrix network.
These best practices mean that you will be able to absorb the impact of any
issues that occur, while continuing to provide service.

* [Controller Best Practices](#controller-best-practices)
* [CoPilot Best Practices](#copilot-best-practices)
* [IAM Best Practices](#iam-best-practices)
* [Gateway Best Practices](#gateway-best-practices)
* [Multicloud Transit Best Practices](#multicloud-transit-best-practices)
* [AWS Transit Gateway Orchestrator Best Practices](#aws-transit-gateway-orchestrator-best-practices)
* [Transit FireNet Best Practices](#transit-firenet-best-practices)
* [External Connections (S2C) Best Practices](#external-connections-s2c-best-practices)
* [UserVPN Best Practices](#uservpn-best-practices)

> [!NOTE]
>
> This guide will be updated on an ongoing basis. Contact your Aviatrix account
> representative if you have any questions pertaining to this document.

## Glossary

You can access the following glossary links for more information on Aviatrix
terminology and general cloud networking terminology.

* [Aviatrix Glossary](https://docs.aviatrix.com/docs/enterprise/8.2/reference/general/aviatrix-glossary.md)
* [General Glossary](https://docs.aviatrix.com/docs/enterprise/8.2/reference/general/general-glossary.md)
* [Multicloud Rosetta Stone](https://docs.aviatrix.com/docs/enterprise/8.2/reference/general/cloud-rosetta-stone.md)

## Controller Best Practices

> [!WARNING]
>
> The Aviatrix Controller and CoPilot can both be offline for a period of time
> without impacting the data plane. While the Controller is offline, traffic
> will continue to flow, but routing changes will not be processed.
> Understanding the impact of the Controller being offline will help in
> successful operation of the Aviatrix platform.

1. The Aviatrix Controller is shipped with a

   [self-signed certificate](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/settings/configuration.md#certificate-store)
   . Establish a DNS hostname and install a TLS certificate issued by your
   organization or a recognized certificate authority.

2. Deploy the Aviatrix Controller and CoPilot in the same dedicated VPC.

3. Select and secure a suitable set of public IP addresses for both the
   Controller and CoPilot.

   > [!WARNING]
   >
   > Modifying these addresses will prevent communication between the Controller
   > and gateways. Contact [Support](https://support.aviatrix.com/) in the event
   > of any accidental modification.

4. **[Controller High Availability
   (AWS)](https://docs.aviatrix.com/docs/enterprise/8.2/guides/controlplane/controller-ha-aws.md)**: Configure the Aviatrix Controller to automatically restore
   itself in the event of a system issue.

5. **[Controller
   Security Group Management](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/settings/configuration.md#configure-security-settings)**: Configure the Aviatrix Controller to manage
   security groups to restrict connectivity between Controller and Gateways as
   well as Aviatrix CoPilot. This prevents potential downtime or loss of
   visibility caused by user induced errors when managing Access Control Lists.

6. **[Controller Backup and
   Restore](https://docs.aviatrix.com/docs/enterprise/8.2/guides/maintenance/controller-backup-restore.md)**: The Controller orchestrates the configuration of your cloud
   network environment and should be periodically backed up to the appropriate
   AWS/Azure/Google account. If a replacement Controller is launched, you can
   restore the configuration data from your backup. Configure cloud storage
   accounts to replicate across regions in the event of a cloud provider outage.

7. **[Controller Disk/CPU/Memory Sizing Recommendations](https://legacy.docs.aviatrix.com/documentation/latest/getting-started/controller-platform-requirements.html)**

   > [!WARNING]
   >
   > Since these recommendations may change over time, review and ensure your
   > environment matches current Aviatrix sizing guidelines.

8. **[[SAML](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/administration/user-access.md#access-management)
   Authentication](https://docs.aviatrix.com/docs/enterprise/8.2/guides/platform-administration/copilot-saml-authentication)**: Enable SAML-based authentication and role-based access
   controls to the Aviatrix platform.

9. **Build a development environment**: Follow the DevOPS lifecycle and
   establish a development environment comprised of a Controller and CoPilot
   which includes a subset of features and test applications.

10. **Restrict access to the Aviatrix Controller and CoPilot**: Access can be
    restricted by means of a Web Application Firewall (WAF) and Web ACLs, which
    allows your UserVPN clients to authenticate to the SAML endpoint without
    allowing access to the Controller. Access to the Controller from WAF can be
    limited with access controls.

    As an alternative,

    [access can be restricted](https://docs.aviatrix.com/docs/enterprise/8.2/reference/controlplane/copilot-ip-access-management.md)
    via configuration in the Controller and CoPilot.

11. **[Logging](https://docs.aviatrix.com/docs/enterprise/8.2/guides/monitoring/aviatrix-logging.md#aws-cloudwatch)**: Export
    logs to one of the supported integrations.

## CoPilot Best Practices

1. Aviatrix CoPilot is shipped with a self-signed certificate. Establish a DNS
   hostname and install a TLS certificate issued by your organization or a
   recognized certificate authority.

2. **[Deploy CoPilot](https://docs.aviatrix.com/docs/enterprise/8.2/guides/controlplane/deployment-methods.md)**: CoPilot
   provides important visibility into your environment. Choose the deployment
   method that best suits your needs. Deploy the Aviatrix Controller and CoPilot
   in the same dedicated VPC.

3. **[Notification and
   Alerting](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/monitor/notifications.md#view-alerts)**: By configuring

   [proactive alerting](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/monitor/notifications.md#alert-configurations)
   of gateways, VPN tunnels, and other network components, you can receive
   alerts in case of any failures or performance degradation. When creating
   alerts, establish severity levels for your environment to ensure prompt
   response based on the issue detected.

   Use the CoPilot

   [webhook](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/monitor/notifications.md#recipients)
   feature to integrate Aviatrix with your organizations' alerting tools for
   faster detection and resolution.

   Ensure that you enter at least one email address on the Monitor >
   Notification > Recipients tab so that you are notified when the alert
   conditions are met.

   Recommended metrics to use in alerts:

   **Controller/CoPilot System Metrics**

   | Value | |
   | - | - |
   | CPU Idle | \<20% |
   | CPU Used (%) | >= 89% |
   | Memory Available (%) | \< 30% |
   | Disk Free (%) | \< 6% |
   | Memory Used (%) | more than 89 (%) |

   **Gateway Health Metrics**

   | Metric | Condition |
   | - | - |
   | Gateway Status | Any change |
   | | Available conditions are Down, Keep Alive Fail, Config Fail, and Upgrade Fail. |
   | Underlay Connection Status | Any change |
   | Connection Status | Any change |
   | BGP Peering Status | Any change |

   **Gateway Network Metrics**

   | Metric | Condition |
   | - | - |
   | Limit Exceeded Rate (PPS) | > 40 pkt/s |
   | Bandwidth Ingress Limit Exceeded Rate | > 40 pkt/s |
   | Bandwidth Egress Limit Exceeded Rate | > 40 pkt/s |
   | Conntrack Limit Exceeded Rate | > 40 pkt/s |
   | Packet Drop (%) | more than 1(%) |
   | PPS Limit Exceeded Drop (%) | more than 1 (%) |
   | Packets Dropped while Receiving | > 40 pkt/s |
   | Packets Dropped During Transmission | > 40 pkt/s |
   | Errored Packets Received Rate | > 40 pkt/s |
   | Errored Packets Transmitted Rate | > 40 pkt/s |

   Aviatrix CoPilot includes default alerts that should be used in all
   environments to ensure the healthy operation of the network. Ensure that you
   assign the appropriate recipients to these alerts, and that alerts are
   reviewed and acted upon in a timely manner.

   The following are default alerts and cannot be deleted:

   * [Global Control Plane Health](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/monitor/notifications.md#view-alerts)
   * [Global Memory Swap Surge](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/monitor/notifications.md#view-alerts)
   * [Global Network Health](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/monitor/notifications.md#view-alerts)

4. **[CoPilot
   Security Group Management](https://docs.aviatrix.com/docs/enterprise/8.2/guides/controlplane/copilot-controller-settings.md#enable-security-groups)**: In addition to Controller and Gateway
   Security Group management, also enable CoPilot Security Group Management to
   restrict access to the CoPilot instance.

5. **[Customize
   Backup Schedules and Counts](https://docs.aviatrix.com/docs/enterprise/8.2/guides/maintenance/controller-backup-restore-copilot#modify-backup-schedule)**: Retain up to 60 days of Controller
   backups, to ensure quick recovery in the event of any issues. Determine a
   reasonable number of backups for your environment. Prior to network change
   windows, review backups and/or create a manual backup. Aviatrix recommends
   retaining an offline copy of your backup during upgrades. In addition to
   Controller backups, enable

   [CoPilot backups](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/settings/maintenance.md)
   to the Controller.

6. **[CoPilot
   Disk/CPU/Memory Sizing Recommendations](https://docs.aviatrix.com/docs/enterprise/8.2/reference/controlplane/copilot-platform-requirements.md)**

   > [!WARNING]
   >
   > Since these recommendations may change over time, review and ensure your
   > environment matches current Aviatrix sizing guidelines.

7. **[RBAC](https://legacy.docs.aviatrix.com/documentation/latest/platform-administration/accounts-and-users/users-and-permissions.html)**
   (Role-Based Access Control): Limit access for non-administrators to read-only
   accounts. When assigning access, always follow the principle of least
   privilege.

8. **SAML**: Only configure if not already configured in Controller.

## IAM Best Practices

1. **[Aviatrix Account
   Audits](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/administration/audit.md#view-audit-logs)**: Use the Account Audit feature to be informed about when your
   policies deviate from Aviatrix standards. Audit failures are displayed in the
   CoPilot (Administration > Audit) and Controller dashboards.

## Gateway Best Practices

1. **[Configure
   High Availability for Gateways and Tunnels](https://docs.aviatrix.com/docs/enterprise/8.2/guides/gateways/gateway-ha-about.md#create-ha-gateway-instance)**: Aviatrix recommends
   deploying multiple HA gateways in different Availability Zones (AZs) to
   ensure redundancy. This helps distribute network traffic and provides
   automatic failover in case of a gateway failure.

2. **[Enable Single AZ HA](https://legacy.docs.aviatrix.com/documentation/latest/network/gateway-single-az-ha.html)**:
   In non-production or non-critical environments which do not employ multiple
   gateways, Aviatrix recommends that gateways be deployed with single AZ HA
   enabled. This helps ensure uptime in the event of any issues. This is
   enabled by default if launched from the Controller or CoPilot. If using
   Terraform, you must enable the appropriate flag.

3. **[Auto
   Right-Sizing](https://docs.aviatrix.com/docs/enterprise/8.2/concepts-architectures/architecture/sizing/auto-right-sizing-about.md)**: Easily increase or decrease gateway size for gateway
   instances based on provided recommendations.

   To schedule gateway resize operations, use

   [Auto Cycles](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/cloud-fabric/scaling.md#auto-cycles)

   under **Cloud Fabric** > **Scaling** > **Auto Cycles**.

   > [!NOTE]
   >
   > The legacy Gateway Scaling feature (Policies, Recommendations, Events
   > tabs) is deprecated and no longer available to new users. See&#x20;
   > [Gateway Scaling (Deprecated)](https://docs.aviatrix.com/docs/enterprise/8.2/reference/gateways/gateway-scaling.md)&#x20;
   > for details.

4. **[Adjusting Aviatrix Controller
   Gateway Keepalive Timers](https://docs.aviatrix.com/docs/enterprise/8.2/reference/gateways/gateway-keepalive.md)**: Recovery times depend on the selected HA
   strategy. Align your objectives for each environment with the Aviatrix
   guidelines for recovery.

5. **[Gateway sizing recommendations](https://legacy.docs.aviatrix.com/documentation/latest/network/gateway-size.html)**:
   While each environment is different, Aviatrix provides recommendations on
   typical instance sizes for gateway deployments by cloud provider. Ensure
   that your environmental needs match the deployed instance sizes. Consider
   factors such as the number of VPCs, anticipated bandwidth requirements, and
   any specific performance needs of your applications.

   Other gateway settings you can configure for resiliency are:

   * **[Modifying TCP MSS Sizes](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/settings/maintenance.md)**: The
     recommended maximum for AWS, Azure, and OCI is 1370 bytes. The recommended
     maximum for GCP is 1330 bytes. The default is usually sufficient.
   * **[IPsec Anti-Replay Window](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/settings/maintenance.md)**: The
     default size (1) is usually sufficient.

## Multicloud Transit Best Practices

1. **[Multi-Region
   Design Patterns](https://docs.aviatrix.com/docs/enterprise/8.2/concepts-architectures/architecture/connectivity/multi-cloud-design-patterns.md)**: Aviatrix recommends implementing a transit network
   architecture to centralize and simplify network connectivity. By using a
   hub-and-spoke model, you can connect multiple VPC or VNet environments to a
   central transit hub, which provides redundancy and centralized control. Also
   see

   [Overview of Aviatrix Multicloud Transit Network](https://docs.aviatrix.com/docs/enterprise/8.2/concepts-architectures/architecture/connectivity/transit-network-faq.md)
   .

   Transit architectures should span a minimum of two cloud provider regions.
   Ensure applications are designed to operate in the event of a single regional
   outage.

2. **[Multicloud Deployments](https://legacy.docs.aviatrix.com/documentation/latest/network/mctn-workflows.html)**:
   Connect different cloud providers using MultiCloud Transit Peering.

3. **[Multi-Tier
   Transit](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/cloud-fabric/gateways.md#edit-a-transit-gateway)**: Use in larger deployments. You can add transit layers to
   simplify peerings.

## AWS Transit Gateway Orchestrator Best Practices

Only do the following if using the

[Aviatrix AWS TGW Orchestrator](https://docs.aviatrix.com/docs/enterprise/8.2/concepts-architectures/components/tgw/tgw-landing-page.md)
feature.

1. \*\*Enable

   [TGW nightly audit of routes](https://docs.aviatrix.com/docs/enterprise/8.2/guides/connectivity/tgw/tgw-overview.md#tgw-audit-settings)
   \*\*: This ensures routing consistency when working in TGW Orchestrator
   environments.

2. **Enable
   [TGW route approval](https://legacy.docs.aviatrix.com/documentation/latest/network/tgw-approval.html)**:
   This ensures the predictability of your network routing. Confirm and
   advertise approved routes learned over Direct Connect or VPN connections.

3. **[Use Transit Gateway
   Peering](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/networking/connectivity.md#aws-tgw)**: Connect Transit Gateways in multiple accounts and regions
   together with Transit Gateway Peering for redundancy.

## Transit FireNet Best Practices

1. \*\*Simplify the

   [insertion](https://docs.aviatrix.com/docs/enterprise/8.2/guides/security/firenet/firewall-launch-attach.md)
   of Next Generation Firewalls with
   [Transit FireNet](https://docs.aviatrix.com/docs/enterprise/8.2/guides/security/firenet/transit-firenet-overview.md)
   \*\*: With Transit FireNet, Aviatrix simplifies the insertion and health-check
   of firewalls in a topology. Transit FireNet can filter traffic in both
   East/West and North/South directions and you can select inspected traffic.
   Health monitors ensure continuity of service in the event of a firewall
   outage.

2. **Deploy Across Availability Zones**: Transit FireNet is designed to provide
   high availability and fault tolerance. Deploy multiple Transit FireNet
   gateways across different availability zones and regions to ensure redundancy
   and resiliency. Deploy firewalls and Transit FireNets in matching
   availability zones to optimize latency.

3. **[Firenet Vendor
   Integrations](https://docs.aviatrix.com/docs/enterprise/8.2/guides/security/firenet/firenet-vendor-integration.md)**: To simplify deployment of Next Generation Firewalls
   (NGFW), use existing Aviatrix vendor integrations to rapidly deploy and
   prepare Palo Alto, Check Point, and Fortinet FortiGate firewalls in the
   cloud.

   Transit FireNet allows for the use of almost every NGFW (Next Generation
   Firewall) appliance. However, existing firewall integrations can help improve
   the speed of deployment by pre-configuring routes on the firewalls.

   Firewall instances should be deployed in HA pairs and designed to meet the
   throughput needs of your environment.

## External Connections (S2C) Best Practices

1. **Deploy Across Regions**: Deploy Site2Cloud connections across provider
   regions for redundancy.

2. **[Active-Active HA](https://legacy.docs.aviatrix.com/documentation/latest/network/externaldevice-settings.html#active-active-ha)**:
   To achieve redundancy for VPN connections, Aviatrix supports an active-active
   HA architecture. By establishing multiple tunnels between your on-premises
   data center and the cloud, you can ensure continuous connectivity even if one
   tunnel or gateway fails.

3. **[Use BGP AS Path Prepend](https://legacy.docs.aviatrix.com/documentation/latest/network/bgp-connection-settings.html#as-path-prepend)**:
   When establishing a Site2Cloud connection, review your traffic engineering
   requirements. Use AS Path Prepend when needed to influence traffic flows.

4. **BGP route approval**: Ensure the predictable flow of traffic by enabling
   BGP route approval. This prevents accidental injection of routes.

5. **[Handling
   IP-Overlap](https://docs.aviatrix.com/docs/enterprise/8.2/guides/connectivity/vpn/s2c-configuration-workflow.md#creating-connection)**: In the event of IP overlap between Cloud and on-premises
   environments, or between overlapping cloud environments, build Site2Cloud
   connectivity with Mapped NAT enabled. Mapped NAT simplifies IP address
   translation between existing environments.

6. **[Keeping
   IPSEC Tunnels Active](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/diagnostics/diagnostic-tools.md#run-gateway-diagnostics)**: In environments that may not have regular
   traffic, avoid security association timeouts by enabling Periodic Ping as a
   keep-alive mechanism.

7. **Reduce Convergence Time**: Event Triggered HA reduces convergence time.

8. **[Fine-tune
   detection timers when networks overlap](https://docs.aviatrix.com/docs/enterprise/8.2/guides/connectivity/nat/s2c-overlapping-cidrs-with-fast-convergence.md)**: When on-premises and cloud
   networks overlap, follow Aviatrix recommendations for improving failover
   timers.

   The following settings are also available for resiliency:

   * [Dead Peer Connection](https://legacy.docs.aviatrix.com/documentation/latest/network/externaldevice-settings.html#dead-peer-connection)
   * [Site2Cloud RX Balancing](https://legacy.docs.aviatrix.com/documentation/latest/network/bgp-connection-settings.html#s2c-rx-balancing)
   * [BGP timers and settings](https://legacy.docs.aviatrix.com/documentation/latest/network/bgp-connection-settings.html)

## UserVPN Best Practices

1. **[Establish User VPN Profiles to
   Restrict Access](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/cloud-fabric/uservpn.md#profiles)**: Establish VPN profiles for each environment requiring
   remote access.

   Follow the principle of "least privilege": Create a base Deny-All ruleset and
   add additional access as required. Assign multiple profiles to a user in a
   layered approach via SAML to simplify access management.

2. **[Geographic
   redundancy](https://docs.aviatrix.com/docs/enterprise/8.2/guides/uservpn/user-vpn-gateway-geo-vpn-create.md)**: Deploy UserVPN gateways in geographically redundant
   locations, and use

   [VPN User Accelerator](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/cloud-fabric/uservpn.md)
   when applicable to ensure uptime and low latency connectivity to your cloud
   environments.

3. **[Scale-out](https://docs.aviatrix.com/docs/enterprise/8.2/reference/uservpn/user-vpn-faq.md#scale-out-vpn-solution)**:
   Determine the approach that best suits your needs when deploying VPN
   gateways. Select from either load balancer, round-robin DNS, or
   geographically-based DNS response to address user VPN demands.

4. **[Increase the maximum number of user connections per gateway](https://legacy.docs.aviatrix.com/documentation/latest/uservpn/uservpn-admin-guide/user-vpn-gateway-settings.html#max-connection)**:
   Establish thresholds for usage of each VPN gateway to better distribute load.

5. **[Client certificate sharing](https://legacy.docs.aviatrix.com/documentation/latest/uservpn/uservpn-admin-guide/user-vpn-gateway-settings.html#enable-client-cert)**:
   Do this to reduce provisioning requirements and use your chosen Identity
   Management system to provide role-based controls over access.

6. **[Integrate with SAML](https://docs.aviatrix.com/docs/enterprise/8.2/guides/uservpn/user-vpn-saml-authentication.md)**:
   Integrate VPN deployments with your identity management systems to provide
   uniform controls over authentication, authorization, and accounting.

[Gateway Performance and Sizing](https://docs.aviatrix.com/docs/enterprise/8.2/reference/gateways/gateway-sizing.md)

[Secure VPCs Best Practices Guide](https://docs.aviatrix.com/docs/enterprise/8.2/reference/best-practices/secure-vpcs-best-practice.md)

## Related Topics

* [SAML Authentication](https://docs.aviatrix.com/docs/enterprise/8.2/reference/ui/administration/user-access.md#view-access-management)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.