- Newest
- Most votes
- Most comments
Hello,
VPC Block Public Access impacts internet-facing Network and Application Load Balancers.
Block Public Access Basics
To allow access to your internet-facing Load Balancers, the best option would likely be to exclude your public subnets from the Block Public Access VPC Feature. By doing this, your NAT gateway will also function properly again.
For the NAT Gateway, you can also use an egress-only exclusion.
Block Public Access to VPCs and Subnets
Recommend checking the launch blog
Granular Control with Exclusions
We understand that some resources within a VPC may require bidirectional internet access. Or, you may have use cases, such as centralized traffic inspection, that require an egress-only internet path that Amazon VPC Block Public Access bidirectional or ingress-only block would otherwise reject. To address this need, Amazon VPC Block Public Access includes granular exclusion capabilities. Administrators can specify individual VPCs or subnets to exclude from Amazon VPC Block Public Access enforcement, allowing for targeted internet access where necessary. You can configure these exclusions to permit either all (bidirectional) or only outbound (egress-only) internet access. Like ingress-only block, when you allow an egress-only exclusion, egress traffic from a VPC or subnet is permitted only from NAT Gateways and EIGWs.
Relevant content
asked a year ago
Thank you Brandon, this resolved the issue for me.