Skip to content

combined Ingress and Egress inspection Architectures

0

Dear Team - I was going through below post about "Source IP visibility for combined Ingress and Egress inspection Architectures".

**https://repost.aws/articles/ARYy1Pfr4BQOGvxntapZBgSQ/source-ip-visibility-for-combined-ingress-and-egress-inspection-architectures **

As per above, it is recommended to deploy two endpoints in each AZ, one for ingress and one for egress. However, if i dont want Source-IP visibility for ingress traffic, can i use single aws network firewall endpoint in inspection VPC for both ingress and egress inspection?

Thanks

  • You can connect AWS firewall to TGW using native connection. This can be used for both ingress and egress

asked a year ago401 views

2 Answers
0

Yes, you can use a single AWS Network Firewall endpoint in your inspection VPC for both ingress and egress inspection if you don't require source IP visibility for ingress traffic.

The recommendation to deploy two separate endpoints per availability zone (one for ingress and one for egress) is specifically designed to maintain visibility of the original source IP addresses in both traffic directions. This dual-endpoint approach is necessary because of how AWS decouples inspection from NAT functions - NAT Gateway handles SNAT (Source NAT) while Elastic Load Balancers handle DNAT (Destination NAT).

If you don't need to preserve the original source IP visibility for ingress traffic, you can simplify your architecture by using a single Network Firewall endpoint. This would reduce costs and simplify your routing configuration, though you would lose the ability to see the original client IP addresses before they're translated by the load balancer.

When implementing this single-endpoint approach, you'll need to carefully configure your route tables to ensure all traffic flows through the firewall endpoint appropriately. You can deploy Network Firewall either in a centralized model (in a dedicated security VPC) or in a distributed model (within each application VPC), depending on your overall network architecture and security requirements.

Just be aware that with a single endpoint, you'll be making a trade-off between architectural simplicity and the granularity of your traffic inspection capabilities.
Sources
Source IP visibility for combined Ingress and Egress inspection Architectures | AWS re:Post
IGW->NAT->NFW vs IGW->NFW->NAT | AWS re:Post
Architecture overview - AWS Network Firewall

answered a year ago

AWS
EXPERT

reviewed 8 months ago

0

Hi there,

In the case that source IP visibility is not needed for Ingress traffic, then you can use the same firewall endpoint or set of firewall endpoints for both the Ingress and Egress traffic.

When using the firewall endpoints for source IP visibility in both directions, you need two firewall endpoints because they need to be placed at different points in the traffic flow. Since you only need the Egress source IP visibility, you can place the endpoint(s):

  1. Between an IGW and Public subnet (containing a NAT Gateway or Load Balancer)
  2. Between the Public and Private Subnets
AWS

answered 10 months ago

AWS
EXPERT

reviewed 8 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.