- Newest
- Most votes
- Most comments
Did you ensure the public subnets' route table has a route for 0.0.0.0/0 targeting the IGW? Should be a similar setup for the private subnets with the 0.0.0.0/0 route targeting the NAT GW.
So there's a development, I think I found a solution. Previously I was setting up the database cluster in the same cdk stack where I was creating VPC, subnets, route tables, etc. I was creating the cluster after these resource creations, but it was throwing the above mentioned error. The error thrown there also didn't list any available subnet types. So I deployed the stack without the cluster creation code. I created a new stack and put the code there and it got deployed smoothly. Thus it seems I can't put the DB Cluster creation code in the same stack where I'm creating the VPC for the same. Can somebody explain why that's the case?
I am having the same issue. It's like you can't force the AWS CDK to make one resource first. Even the dependencies don't work.
Relevant content
- Accepted Answerasked 20 days ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago
Yes Christian, I have setup both. I updated the question with supporting screenshots.