Open rantoniuk opened 6 months ago
Yes if you don't specify props.subnets
it would filter and pick up with { subnetType: ec2.SubnetType.PRIVATE_WITH_EGRESS }
, which you don't have in your use case. So you will need to specify props.subnets
.
I would challenge the fact of using PRIVATE_EGRESS as the default - having a VpcLink already means that someone is probably looking for strict security so:
I know it's just an opinion but simplicity of the usage of constructs and minimising the number of props overrides is important in my opinion. Up to you to decide though!
Yeah I guess we need to improve the doc here.
I suggested something else rather than improving the docs.
Describe the bug
VPC defined as:
When trying to deploy the below APIGW definition:
Expected Behavior
VpcLink is created using Isolated subnets automatically.
Current Behavior
Reproduction Steps
As above.
Possible Solution
Workaround:
Additional Information/Context
No response
CDK CLI Version
2.129.0
Framework Version
No response
Node.js Version
18.18.2
OS
MacOS
Language
TypeScript
Language Version
No response
Other information
No response