From 97da0d8f5d2b78bff15a456b91022a9b2d03d2d0 Mon Sep 17 00:00:00 2001 From: Neta Nir Date: Thu, 26 Dec 2019 23:31:09 -0800 Subject: [PATCH] docs(vpc): fromLookup() allows asymmetric vpc import --- packages/@aws-cdk/aws-ec2/README.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/packages/@aws-cdk/aws-ec2/README.md b/packages/@aws-cdk/aws-ec2/README.md index 76a0fa2918e72..19e931eef508d 100644 --- a/packages/@aws-cdk/aws-ec2/README.md +++ b/packages/@aws-cdk/aws-ec2/README.md @@ -235,12 +235,6 @@ The CDK CLI will search for the specified VPC in the the stack's region and account, and import the subnet configuration. Looking up can be done by VPC ID, but more flexibly by searching for a specific tag on the VPC. -The import does assume that the VPC will be *symmetric*, i.e. that there are -subnet groups that have a subnet in every Availability Zone that the VPC -spreads over. VPCs with other layouts cannot currently be imported, and will -either lead to an error on import, or when another construct tries to access -the subnets. - Subnet types will be determined from the `aws-cdk:subnet-type` tag on the subnet if it exists, or the presence of a route to an Internet Gateway otherwise. Subnet names will be determined from the `aws-cdk:subnet-name` tag