Open tpflueger opened 5 hours ago
The error is thrown at Ipv6Addresses.amazonProvided() > AmazonProvided.createIpv6CidrBlocks() (invoked from here > Fn.cidr() > FnCidr().
Since AmazonProvided
Ipv6Addresses is used, it expects subnet configuration to be created.
yes subnet configuration is like the topology definition of your subnets for this vpc which tells the subnet cidr, subnet count as well as the mask, which is required for createIpv6CidrBlocks
.
@pahud Thanks for elaborating the design.
Describe the bug
Our initial CDK setup uses the VPC construct but delays the creation of subnets until later. Note, this worked but it may not be the way CDK is intended to be used. Switching to dual stack IPV4/IPV6, the construct now requires subnets to be defined.
Regression Issue
Last Known Working CDK Version
No response
Expected Behavior
An ipv6 cidr block to be created that I could use for later subnet creation.
Current Behavior
CDK throws an exception.
Unhandled exception. System.Exception: Fn::Cidr's count attribute must be between 1 and 256, 0 was provided.
Reproduction Steps
Possible Solution
Is subnet now a requirement? If not, it might be useful to allow specifying the Ipv6 CIDR block size.
Additional Information/Context
No response
CDK CLI Version
2.160.0
Framework Version
No response
Node.js Version
v22.1.0
OS
Windows 11
Language
.NET
Language Version
.NET 8.0.402
Other information
No response