(EC2): document how to workaround Network ACL rule 100
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
The default NACL created with a custom VPC has a default "100 - Allow All" ingress rule. This should not be since we can't delete rules after the fact thru the CDK.
### Reproduction Steps
### What did you expect to happen?
### What actually happened?
### Environment
- **CDK CLI Version :**
- **Framework Version:**
- **Node.js Version:**
- **OS :**
- **Language (Version):**
### Other
---
This is :bug: Bug Report
Contributor guide
Research direction
Start by reviewing the custom VPC and default NACL behavior described in the issue, including the linked screenshot, and inspect the AWS CDK documentation for Network ACL rule management. Done means adding a clear, tested workaround for the rule 100 limitation to the relevant documentation, with enough context for users to apply it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100