Blocked using option 1
I was following the first option Add an additional IPv4 CIDR block as a secondary CIDR
. Where in current VPC we have AZ1 and AZ2, so I added a secondary CIDR block to have a AZ3, but here I'm running into an issue in exportVpc function, its not able to update the subnet IDs for the AZ3, as it says that the export VpcSubnetIds cannot be updated as it is already in use by Load balancer.
As we are doing changes in production, we cannot delete the existing Load balancer. So is there a way where we can export the AZ3 and update load balancer to have all the 3 AZs.
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
I think the first solution is Good, but this does not support automation if you see here in resource "Type" : "AWS::EC2::VPCCidrBlock", CIDRBLOCK is a string and it will not support an array please implement an api for this resource "AWS::EC2::VPCCidrBlock" to support both CIDR and automation
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
Relevant content
- asked 2 years ago
- asked 9 months ago
- Accepted Answerasked 4 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago