aws/aws-cdk

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

Open

#13,220 创建于 2021年2月23日

在 GitHub 查看
 (10 评论) (3 反应) (0 负责人)TypeScript (10,710 star) (3,530 fork)batch import
@aws-cdk/aws-ec2bugdocs/inlinedocumentationeffort/smallgood first issuep2

描述

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

贡献者指南

技术栈
typescriptaws
领域
cloudinfrastructure
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
2
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Basic CDK knowledgeFamiliarity with VPC and NACLs
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
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.