Option 1 - Edge Protection Deployment
This deployment is designed to protect servers that primarily receive connections from the internet and is best suited to environments that require the following:
- A simple network design that protects web servers.
- Deployment of multiple virtual appliances.
- Inspection between the VPC and the Internet as well as between the VPC and a VPN gateway.
- A single VPC — this deployment option does not require Transit Gateways.
- Third party appliance integration that follows AWS best practices.
This deployment option does not indicate an IP address for the true source instance when a NAT Gateway is used for outbound internet traffic.
This is the deployment that we will be using in our workshop 😊
Option 2 - Centralized Network Appliance with Gateway Load Balancer for Inbound Traffic
This deployment is designed to protect servers that primarily receive connections from the internet.
This deployment option is best suited to environments that require the following:
- An environment that requires centralized security inspection for multiple VPCs across different AWS accounts.
- An environment that includes one or multiple Workload VPCs.
- A separate VPC (referred to as the Security VPC in the image below) where the Network Security virtual appliance and the Gateway Load Balancer are located.
- Traffic that flows through the Gateway Load Balancer VPC endpoint, located in a Workload VPC, without leaving the AWS network.
Refer to the image below for details on the environment structure and routing for this deployment. The numbered arrows represent the order of the flow of traffic through the environment. Green represents the request and orange represents the response.
Dynamic auto-scaling and Inspection Bypass mode are not yet supported for Gateway Load Balancer in Network Security.
Option 3 - Centralized Network Appliance with Gateway Load Balancer for Outbound or Lateral Traffic:
This deployment is designed for AWS architectures that primarily send traffic from EC2 instances to the internet and/or between EC2 instances in different Workload VPCs.
This deployment option is best suited to environments that require the following:
- More than one Workload VPC that needs protection at the same time by a centralized Security VPC
- Environments that use Transit Gateways.
Refer to the image below for details on the environment structure and routing for this deployment. The numbered arrows represent the order of the flow of traffic through the environment. Green represents the request and orange represents the response.
This topology does not inspect inbound connections.