aws-ec2 Allow the Developer to Assign IP addresses to SubNet

[slipdexic]

Note: for support questions, please first reference our documentation, then use Stackoverflow. This repository's issues are intended for feature requests and bug reports.

• I'm submitting a ...

  • 🪲 bug report
  • 🚀 feature request
  • 📚 construct library gap
  • ☎️ security issue or vulnerability => Please see policy
  • ❓ support request => Please see note at the top of this template.

• What is the current behavior?
  If the current behavior is a 🪲bug🪲: Please provide the steps to reproduce
  Currently, when you create a VPC and you add your subnets , these can only be in the SubNetType Ranges (Public, PRivate, Isolated)
  for each of these, in the SubnetConfiguration you can only allocate a CidrMask.
  The actual IP ranges used are allocated by the template.

• What is the expected behavior (or behavior of feature suggested)?
  Allow the developer to assign the actual IP range they wish to use for there subnets.
  This is what users have generally done to date if using cloud formation or via the API.

• What is the motivation / use case for changing the behaviour or adding this feature?
  I have been given a design brief that details out exact subnets, IP address ranges, NACL, Routing etc. CDK does not allow the user to follow such a brief.

• Please tell us about your environment:

  • CDK CLI Version: 1.3.0
  • Module Version: xx.xx.xx
  • OS: [all ]
  • Language: [all ]

• Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc)

[rix0rrr]

Related to #5927

[github-actions]

This issue has not received any attention in 1 year. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

[slipdexic]

I would still like to see this as a feature.
We have stopped defining the VPC via CDK

[Njk00]

+1