Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ec2 make the cidr_block of ISubnet visible #3951

Closed
1 of 2 tasks
slipdexic opened this issue Sep 5, 2019 · 3 comments
Closed
1 of 2 tasks

ec2 make the cidr_block of ISubnet visible #3951

slipdexic opened this issue Sep 5, 2019 · 3 comments
Labels
@aws-cdk/aws-ec2 Related to Amazon Elastic Compute Cloud effort/medium Medium work item – several days of effort feature-request A feature should be added or improved. p2

Comments

@slipdexic
Copy link
Contributor

slipdexic commented Sep 5, 2019

🚀 Feature Request

General Information

  • 👋 I may be able to implement this feature request
  • ⚠️ This feature might incur a breaking change

Description

Currently when you create a VPC ,
The VPC automatically assigns a CIDR range to each subnet , but this is not made visible to the stack.
So if you now wish to create a security group or NetworkAccessConton ,VPN static route etc
you have no Idea of what IP range was used until after the stack has deployed

Whilst this is Similar to #3931 they are different , this issue allow the end use to see with the current set up what IP range has been created and making the property visible, the other ticket is more about being able to control that property and may not be possible with the current VPC design.

Proposed Solution

Add to the ISubnet a the CidrBlock property,
and populate it value in CreateSubnet()

Environment

  • CDK CLI Version: 1.6
  • Module Version:
  • OS: all
  • Language: all

Other information

@slipdexic slipdexic added feature-request A feature should be added or improved. needs-triage This issue or PR still needs to be triaged. labels Sep 5, 2019
@SomayaB SomayaB added @aws-cdk/aws-ec2 Related to Amazon Elastic Compute Cloud service/vpc labels Sep 5, 2019
@rix0rrr rix0rrr removed the needs-triage This issue or PR still needs to be triaged. label Sep 9, 2019
@lielran
Copy link

lielran commented Dec 8, 2019

I also didn't find a way to get the CIDR blocks per subnet once the vpc was created.

@corymhall
Copy link
Contributor

Closing this since it is now possible subnets now have ipv2cidrblock

@github-actions
Copy link

github-actions bot commented Mar 8, 2022

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-ec2 Related to Amazon Elastic Compute Cloud effort/medium Medium work item – several days of effort feature-request A feature should be added or improved. p2
Projects
None yet
Development

No branches or pull requests

5 participants