-
Notifications
You must be signed in to change notification settings - Fork 4.5k
VPC: Private subnets (CDK 1.126) are now Isolated subnets (CDK 1.140) #18638
Copy link
Copy link
Closed
Labels
@aws-cdk/aws-ec2Related to Amazon Elastic Compute CloudRelated to Amazon Elastic Compute CloudbugThis issue is a bug.This issue is a bug.needs-triageThis issue or PR still needs to be triaged.This issue or PR still needs to be triaged.
Description
What is the problem?
Regression somewhere between version CDK 1.126 and 1.140.
When performing a VPC lookup in CDK 1.126 and then fetching the private subnets i had multiple results.
IVpc vpc= Vpc.fromLookup(k, VPC_ID, new VpcLookupOptions.Builder().vpcName("xxxxxxxxxxxxxx").build());
vpc.getPrivateSubnets()
But using version CDK 1.140 i have no longer any private subnets. The private subnets have been moved to isolated subnets.
I am not aware that anything have changed on this level!
Reproduction Steps
IVpc vpc= Vpc.fromLookup(k, VPC_ID, new VpcLookupOptions.Builder().vpcName("xxxxxxxxxxxxxx").build());
vpc.getPrivateSubnets()
What did you expect to happen?
CDK 1.140 code:
IVpc vpc= Vpc.fromLookup(k, VPC_ID, new VpcLookupOptions.Builder().vpcName("xxxxxxxxxxxxxx").build());
vpc.getPrivateSubnets()
return the same results as in version CDK 1.126
What actually happened?
VCDK 1.140 does not return any Private subnets.
CDK CLI Version
1.140.0 (build 789f2dc)
Framework Version
No response
Node.js Version
16.10.0
OS
Windows 10
Language
Java
Language Version
Java 11
Other information
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
@aws-cdk/aws-ec2Related to Amazon Elastic Compute CloudRelated to Amazon Elastic Compute CloudbugThis issue is a bug.This issue is a bug.needs-triageThis issue or PR still needs to be triaged.This issue or PR still needs to be triaged.