-
Notifications
You must be signed in to change notification settings - Fork 57
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
AWS::EC2::Subnet - CidrBlock accessible via Fn::GetAtt #166
Comments
Hi there! Is there any news about that? |
Adding my +1 here I'm dynamically building my It would be nice to manage the This would avoid me repeating the I've already had several instances where I attempted to modify the Subnet size, but neglected to do it in the NetworkAclEntry, resulting in debug cycles. |
This was silently implemented and it is available now. The "funny" thing that the |
Quick Sample Summary:
The Subnet resource already supports to get the Ipv6CidrBlocks (big thanks for that!) but not the IpCidrBlocks. As the IPv6 support is not fully implemented in other resources (like you can't use IPv6 on a Site-to-site VPN) we still need to use IPv4 endpoints for Route53 Resolver Inbound Endpoints. This is very over-complicated if you create the Subnet addressing dynamically.
This is how it looks like now (only the relevant parts):
I have to recalculate the Subnet's network range again. I would like to change to something like this:
The text was updated successfully, but these errors were encountered: