Implementing Egress in an Aviatrix-Managed Network

The Aviatrix Distributed Cloud Firewall (DCF) Egress solution offers a comprehensive approach to securing egress traffic to the internet in cloud environments. This solution is designed to enhance visibility, enforce centralized policies, and optimize traffic for performance and cost efficiency. It addresses the growing complexity of managing security across multi-cloud environments by operating within individual VPCs or VNets. By inspecting and enforcing security rules directly in the cloud network where the traffic originates, this approach ensures that all traffic is inspected before it leaves the cloud network, providing real-time visibility and policy enforcement at the spoke level.

Distributed Cloud Firewall (DCF) is the recommended method for configuring egress. If you want to implement egress this way, you must first enable SNAT on the egress Spoke gateways and create DCF policies that use WebGroups.

Access to Egress Security Score features require Controller 8.0 and for the DCF feature to be enabled.

If these are both present:

  • The Security > Egress > Overview tab displays, where you can view a summary of your protected VPC/VNets; the Egress Security Score for those protected VPC/VNets; and view how the Egress Security Score is calculated.

  • You can monitor VPC/VNets from the Security > Egress > Egress VPC/VNets tab.

Applying Local Egress to Spoke Gateways

Local egress ensures that all outbound traffic is inspected and enforced directly within the cloud network where it originates. This provides real-time visibility and policy enforcement at the spoke level, preventing unauthorized access and defending against threats aimed at outgoing traffic.

When you enable local egress, SNAT is automatically enabled. This translates all outbound traffic originating from the Spoke VPC/VNet to use the gateway’s public IP address. Also, the default route on the VPC/VNet changes to point to the Spoke gateway.

  • Use at least t3.medium for an AWS VPC if applying local egress.

  • Use at least Standard_B2ms for an Azure VNet if applying local egress.

Prerequisites

  • Ensure additional CPU resources are created on the Spoke gateway to support Local Egress.

  • Enable Spoke gateways to send traffic to the internet on the Egress VPC/VNets tab.

Monitoring Egress Traffic

Controller 8.0 is required to monitor VPC/VNets.

When you monitor your VPC/VNets, in addition to local egress being applied, your egress traffic is logged, and Aviatrix gateways are deployed within those VPC/VNets.

Applying Egress to Transit Gateways (Legacy)

You should only apply egress to your Transit gateways if you are already using the Egress Control feature in the Aviatrix Controller.

Regardless of if you originally configured egress rules in Aviatrix Controller, or use DCF with WebGroups, you can view statistics on the Analyze tab, and view when rule conditions were met for a VPC/VNet on the FQDN Monitor (Legacy) tab.

You may want to apply egress to your Transit gateways so that they can act as centralized egress points, where outbound traffic from Spoke gateways is inspected and managed before it leaves the cloud network. This setup allows for consistent policy enforcement and visibility across multiple VPC/VNets.

This gathers data from attached Spoke gateways and sends it to the internet.

Prerequisites

Ensure that Transit gateways have Transit Egress Capability enabled.