aws/aws-cdk

(EC2): document how to workaround Network ACL rule 100

Open

#13,220 opened on Feb 23, 2021

View on GitHub
 (10 comments) (3 reactions) (0 assignees)TypeScript (10,710 stars) (3,530 forks)batch import
@aws-cdk/aws-ec2bugdocs/inlinedocumentationeffort/smallgood first issuep2

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. image

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

Tech stack
typescriptaws
Domain
cloudinfrastructure
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic CDK knowledgeFamiliarity with VPC and NACLs
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue asks for documentation on how to workaround the default Network ACL rule 100 that cannot be deleted via CDK. Look at the CDK source code for ec2.NetworkAcl and related constructs to understand the current behavior. Then, based on the discussion in comments, write a documentation entry explaining the limitation and providing a workaround, such as using a custom resource or modifying the NACL via AWS SDK. Place the documentation in the appropriate section of the AWS CDK user guide, likely under the VPC or Network ACL section.