- Newest
- Most votes
- Most comments
When you delete resources that have VPC Block Public Access exclusions before removing the exclusion itself, you may encounter a situation where the exclusion appears as "deleted" but remains in your list of exclusions.
The VPC Block Public Access feature allows you to create exclusions for specific VPCs or subnets to permit either bidirectional (all) or egress-only internet access, even when Block Public Access is enabled at the account level. These exclusions can be created preemptively, even before enabling Block Public Access, to ensure no traffic disruption when the feature is turned on.
While the documentation doesn't specifically mention an automatic cleanup period for "deleted" exclusions, you should be able to use the DeleteVpcBlockPublicAccessExclusion API to completely remove the exclusion from your account. If you're encountering issues with this process, it might be worth contacting AWS Support as this behavior isn't explicitly documented.
Remember that you can manage these exclusions at both the VPC and subnet level, and they're designed to provide granular control over your internet access policies while maintaining your overall security posture.
Sources
DeleteVpcBlockPublicAccessExclusion - Amazon Elastic Compute Cloud
Enhancing VPC Security with Amazon VPC Block Public Access | Networking & Content Delivery
answered a year ago

Thanks, that API call doesn't work as it has been already removed.