You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(ec2-alpha): add multiple NATGW to the VPC using addNatGateway method (#34094)
Closes #<issue number here>.
### Reason for this change
Cannot add multiple NATGW to current VPC construct as it is using the same construct id which cause conflict.
### Description of changes
- Fix the NATGW construct id to be unique using provided subnet.
- Fix the current domain being set in EIP to be `vpc` instead of `vpcId`.
- Fix the validation for subnet IP ranges as those can be unresolved token values referred in VPC construct using vpc.attr.<ipaddressblock> .
### Describe any new or updated permissions being added
NA
### Description of how you validated changes
- Added unit test and integration test for NATGW.
- Added unit test for EIP
### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)
BREAKING CHANGE: The logical ID for the NAT Gateway, defined using the `addNatGateways` method, will be changed, resulting in the NAT Gateway being recreated. Additionally, the domain for the Elastic IP (EIP) will be set to `vpc`, which will also trigger its recreation in the account.
----
*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Copy file name to clipboardExpand all lines: packages/@aws-cdk/aws-ec2-alpha/test/integ.test-import.js.snapshot/integtestmodelDefaultTestDeployAssertCF40BD53.assets.json
0 commit comments