Deploying a Public Subnet Filtering Gateway

Deploying a Public Subnet Filtering gateway

Follow the workflow below.

Launching a Public Subnet Filtering Gateway

  1. In the Aviatrix Controller, navigate to Security > Public Subnet > Add New.

  2. Fill in the fields as shown in the below table.

Setting Value

Cloud Type

AWS

Gateway Name

Input a unique gateway name

Account Name

Select the Access Account

Region

Select the AWS region

VPC ID

Select the VPC in the chosen AWS region

Unused Subnet

Aviatrix Controller creates a public subnet and creates a route table associated with the subnet to launch the filtering gateway

Gateway Size

Select an instance type

Route Table

Select a route table whose associated public subnets are protected.

  1. Click Create.

After the PSF gateway is launched, Ingress traffic from IGW is routed to the gateway in a pass through manner. Egress traffic from instances in the protected public subnets is routed to the gateway in a pass through manner.

Enabling GuardDuty Enforcement

  1. In the Aviatrix Controller, navigate to Security > AWS GuardDuty.

  2. Select an Access Account and AWS Region.

  3. Click Actions > Enable.

Once GuardDuty is enabled, malicious source IP addresses attacking instances in the public subnets in the region will be polled by the Controller. The Controller then programs rules into the filtering gateway to drop these packets.

if you enable AWS GuardDuty without launching the PSF gateway, GuardDuty does not have enforcement functionality.

Enabling Egress FQDN

Once the PSF gateway is launched, you can configure the FQDN feature.

In the Aviatrix Controller, navigate to Security > Egress Control and follow the instructions in the FQDN workflow.