This repository was archived by the owner on Oct 4, 2024. It is now read-only.
Issues with "witness" Third Zone Private Subnet CIDR mask and Ambiguous MMAD / Directory Service parameters #69
Description
Hello - hoping to get some help/support on using this QuickStart in the following way:
- Existing VPC with public and private subnets across two AZs (1a and 1b) in AWS-Gov-East region.
- Do NOT have an AWS Managed Microsoft Directory Services setup nor a self-managed Active Directory
- Will use Third AZ (1c) as the witness zone rather than using 2nd node as witness (looked like this was the "none" option).
- Windows Server 2019 with Windows SQLServer Standard 2019 nodes.
Each time I try to review parameters, I keep getting errors that won't let me continue along 2 lines, either it complains of:
- The CIDR block setting not being of the right format for private subnet 3 (when I specify "witness" for third zone) and give it the actual CIDR for the 3rd private subnet, OR
- there is ambiguity in the template recognizing I want it to create the AWS MMAD - I don't know how to specify the MMAD ID, and then don't know if the domain controller 1 name and domain controller 2 names under the self-managed section are even required. The admin password is under the self-managed section too.
Attaching a document which shows all the of the template settings I'm trying and what it keeps telling me - I have not been able to get past the review and execute the quick start. Please see the top-down comments in the attached file. Thank you for the help. Time sensitive and wanting to get this cluster up very quickly.