Aws-cdk: VPC and Subnet to allow developer to set the Cidr_Block

Created on 4 Sep 2019  路  3Comments  路  Source: aws/aws-cdk

:rocket: Feature Request

General Information

  • [ ] :wave: I may be able to implement this feature request
  • [x] :warning: This feature might incur a breaking change

Description


Currently when you create a VPC , you say how many AZ's and the Cidr_mask for each subnet in the respective ZONE , e.g Public, Private....
The Cidr ranges are then automatically assigned, and also not surfaced.

What I need to do is have control over the ISubnets CidrBlock.
Currently you can only say what the Subnet mask is range (/16 - /28), the CDK/ VPC inside CreateSubnets() calculate and assigns the CidrBlock. it does not even report it back #3951

This is great for a simple environment , but in a enterprise environment this just does not work with complex networks, the design will be passed down IP ranges agreed and assigned a head of a single line of code being written.

Proposed Solution

Allow the enduser/developer/devops person to have the option of assigning the IP ranges (CIRDBlocks) themselves

Environment

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

Other information

@aws-cdaws-ec2 efforlarge feature-request p2

Most helpful comment

@NGL321 , no this is not that is at VPC level I need this at subnet level
I have updated the feature request description .

IMHO new need a more simplistic base VPC class , that we can inherit from, the current one does to much and makes a lot of assumptions (not all networks are symmetrical).
It is a lot of work to create your own custom VPC as I discovering , so I'm feeding back into this project so others in PCI-DSS / HIPPA / locked down environments don't have these issues.

Adding these features give the developer a lot more power and control.

All 3 comments

Hey @slipdexic,

Thank you for submitting a feature request!
I looked in the docs and saw that one of the VPC props is a specific definition for CIDR.
From how I was reading the request, this is what you are asking for.
Please let me know if I am wrong and if it is different functionality you are looking for!
馃樃

@NGL321 , no this is not that is at VPC level I need this at subnet level
I have updated the feature request description .

IMHO new need a more simplistic base VPC class , that we can inherit from, the current one does to much and makes a lot of assumptions (not all networks are symmetrical).
It is a lot of work to create your own custom VPC as I discovering , so I'm feeding back into this project so others in PCI-DSS / HIPPA / locked down environments don't have these issues.

Adding these features give the developer a lot more power and control.

Was this page helpful?
0 / 5 - 0 ratings