fix(ec2-alpha): add multiple NATGW to the VPC using addNatGateway method

[shikha372]

Closes #.

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. .

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

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

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

[aws-cdk-automation]

(This review is outdated)

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[shikha372]

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.

[aws-cdk-automation]

The pull request linter fails with the following errors:

❌ Breaking changes should be indicated by starting a line with 'BREAKING CHANGE: ', variations are not allowed. (found: '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.').

If you believe this pull request should receive an exemption, please comment and provide a justification. A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed, add Clarification Request to a comment.

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 7c98453
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository