docs(ec2): clarify default network ACL rule 100 - #37885
Draft
MukundaKatta wants to merge 1 commit into
Draft
Conversation
MukundaKatta
requested a deployment
to
automation
May 15, 2026 08:08 — with
GitHub Actions
Abandoned
This was referenced Jun 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
Closes #13220.
Reason for this change
AWS creates a default network ACL for every VPC and includes AWS-managed allow-all rule 100 entries. CDK exposes the default ACL ID but CloudFormation cannot remove or replace those default entries, so users need a custom NetworkAcl associated with selected subnets when they want deny-by-default behavior.
Description of changes
Vpc.vpcDefaultNetworkAcl.Subnet.networkAclthat the default ACL includes rule 100 and CloudFormation cannot delete it.NetworkAclassociation as the workaround.Validation
git diff --check