Issues with "witness" Third Zone Private Subnet CIDR mask and Ambiguous MMAD / Directory Service parameters

[emergingdigital]

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.

SIOS-DKCE-QuickStart-20221203.docx

[carrollh]

If you are using the "Existing VPC" option, then your VPC has to already have 3 AZs, and all of the associated subnets and routing configured. You also need to have the AWS Managed AD set up yourself (then you can use its ID in the template). The "Existing VPC" option only creates new cluster nodes and installs SQL on them. Everything else needs to exist before hand.
You also cannot use existing cluster nodes with this quickstart. You can use existing Domain Controllers if you go the Self-managed AD route, but not existing cluster nodes.
I recommend using the "Deploy into a new VPC" option instead.

[emergingdigital]

Heath, Thank you. That helps. Thank you for the reply. Chris -- Chris Wiseman*, *Emerging Digital Concepts NG-CAD-X / Public Safety Solutions *www.ngcadx.com <http://www.ngcadx.com> | www.emergingdigital.com <http://www.emergingdigital.com>* ***@***.*** ***@***.***>* Mobile: (571) 233-7423

…

On Tue, Dec 6, 2022 at 5:45 PM Heath Carroll ***@***.***> wrote: If you are using the "Existing VPC" option, then your VPC has to already have 3 AZs, and all of the associated subnets and routing configured. You also need to have the AWS Managed AD set up yourself (then you can use its ID in the template). The "Existing VPC" option only creates new cluster nodes and installs SQL on them. Everything else needs to exist before hand. You also cannot use existing cluster nodes with this quickstart. You can use existing Domain Controllers if you go the Self-managed AD route, but not existing cluster nodes. I recommend using the "Deploy into a new VPC" option instead. — Reply to this email directly, view it on GitHub <#69 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABXHJUA6WO42NGFJAP37RETWL66YPANCNFSM6AAAAAASU3H2FA> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[emergingdigital]

I already have a working VPC with everything but a replicated, clustered DB. We thought AWS Gov would support the RDS Custom option but alas, it does not, thus SIOS DKCE on SQL Server Standard nodes is our best option. Chris -- Chris Wiseman*, *Emerging Digital Concepts NG-CAD-X / Public Safety Solutions *www.ngcadx.com <http://www.ngcadx.com> | www.emergingdigital.com <http://www.emergingdigital.com>* ***@***.*** ***@***.***>* Mobile: (571) 233-7423

…

On Tue, Dec 6, 2022 at 5:45 PM Heath Carroll ***@***.***> wrote: If you are using the "Existing VPC" option, then your VPC has to already have 3 AZs, and all of the associated subnets and routing configured. You also need to have the AWS Managed AD set up yourself (then you can use its ID in the template). The "Existing VPC" option only creates new cluster nodes and installs SQL on them. Everything else needs to exist before hand. You also cannot use existing cluster nodes with this quickstart. You can use existing Domain Controllers if you go the Self-managed AD route, but not existing cluster nodes. I recommend using the "Deploy into a new VPC" option instead. — Reply to this email directly, view it on GitHub <#69 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABXHJUA6WO42NGFJAP37RETWL66YPANCNFSM6AAAAAASU3H2FA> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>