Skip to content
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.

Getting a Secondary1NodeSubnet template fail with default settings. #25

Closed
adanklefsensection opened this issue Feb 28, 2018 · 8 comments

Comments

@adanklefsensection
Copy link

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}

@vsnyc
Copy link
Member

vsnyc commented Feb 28, 2018

What was the id of the Secondary1NodeSubnet that you selected?

@adanklefsensection
Copy link
Author

image

@adanklefsensection
Copy link
Author

Used the 'Quickstart for new VPC here'

https://docs.aws.amazon.com/quickstart/latest/mongodb/step2.html

@vsnyc
Copy link
Member

vsnyc commented Feb 28, 2018

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?

@vsnyc
Copy link
Member

vsnyc commented Feb 28, 2018

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.
Thanks for reporting this!

@adanklefsensection
Copy link
Author

Very awesome, that's probably exactly what it is. I did opt in for longer resource ids. Good looking out!

@vsnyc
Copy link
Member

vsnyc commented Feb 28, 2018

This is now fixed, please try again.

@vsnyc vsnyc closed this as completed Feb 28, 2018
@adanklefsensection
Copy link
Author

Got further in the chain:
image

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants