-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VPC error on NAT Gateway strategy #931
Comments
What version of awsx are you using? It appears the pulumi CLI plugin listing isn't picking it up correctly. |
awsx 1.0.0-beta.5 |
I noticed that you're using a /16 for both the VPC CIDR and the subnet CIDRs. Normally the subnet CIDR would be something like /19, /20, or similar. Could you try adjusting the CIDR for the subnets to see if the error still persists? |
@aaronkao This should be fixed in a more recent version of AWSX. Try |
Having a similar issue with YAML:
Error:
|
This was fixed in #885 |
What happened?
Trying to create VPC with AWSX. Upon specifying subnetSpecs an error is given on NAT Gateway strategy
Error: If NAT Gateway strategy is 'OnePerAz' or 'Single', both private and public subnets must be declared. The private subnet creates the need for a NAT Gateway, and the public subnet is required to host the NAT Gateway resource.: Error: If NAT Gateway strategy is 'OnePerAz' or 'Single', both private and public subnets must be declared. The private subnet creates the need for a NAT Gateway, and the public subnet is required to host the NAT Gateway resource.
Steps to reproduce
Expected Behavior
VPC to be created
Actual Behavior
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: