Step 3: Create the Windows Server Failover Cluster

Enable the Failover Clustering Feature

Run the following Powershell Script on each cluster node:

Install-WindowsFeature -Name Failover-Clustering -IncludeManagementTools

Run Cluster Validation

Run the following command on one of the nodes to validate the cluster:

Test-Cluster -Node sios1,sios2

The validation report will show some warnings about a single network interface and no shared storage, you can ignore those warnings as those are expected in a SANless cluster running in AWS.

Create the Cluster

When creating the cluster in AWS it is important to do it via PowerShell rather than the WSFC interface. When we create the cluster we will use two of the secondary IP addresses we added to the interfaces in an earlier step.

Run the following PowerShell command on one of the cluster nodes:

New-Cluster -Name sapcluster -Node sios1,sios2 -StaticAddress 10.0.2.151, 10.0.3.151 -NoStorage

Add the File Share Witness

First create a folder on another server in an 3rd availability zone. Once you have the folder created, share it and give the Cluster Name Object (CNO) Change permissions at the Share level and Modify permissions at the Security level.

Once the permissions are assigned, run the following PowerShell command to update the cluster quorum to add this file share witness.

Set-ClusterQuorum -FileShareWitness \\dc1\Sapcluster