This repository has been archived by the owner on Jan 9, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 113
Getting a Secondary1NodeSubnet template fail with default settings. #25
Comments
What was the id of the Secondary1NodeSubnet that you selected? |
Used the 'Quickstart for new VPC here' https://docs.aws.amazon.com/quickstart/latest/mongodb/step2.html |
I see. Do you happen to have the stack still up? If you go to the nested VPCStack in CloudFormation console and look at the Outputs tab, what is the value of PrivateSubnet2AID and PrivateSubnet3AID? |
This is likely happening because the AWS account is opted in for longer resource ids. I'll check in a fix and comment when the issue is resolved. |
Very awesome, that's probably exactly what it is. I did opt in for longer resource ids. Good looking out! |
This is now fixed, please try again. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Deploying in Ohio region with 3 AZ, changing size from 400 to 25; everything else is default. Getting:
Parameter 'Secondary1NodeSubnet' must match pattern subnet-[0-9a-z]{8}
The text was updated successfully, but these errors were encountered: