SQL server standard 2016 fail over cluster Amazon AWS
I did a presentation on this during the summer @ SQL Saturday - LA and you have a few options.  In some cases, you need clustering if Mirroring isn't an option and AlwaysOn AGs require cross database (but same instance I believe) transactions using MSDTC on some versions of SQL Server.  

Thus in order to provide failover clustering support in AWS I used an AWS Storage Gateway to act as a routable SAN.  This was simple to setup and was secured easily via the AWS security groups.  We then used mirroring to mirror to Azure and on Azure I used the new SQL and Windows 2016 shared storage direct solutions which are an option for AWS if you use Windows 2016.  

Here are the relevant slides on setting up a storage gateway:

-Select the "Storage Gateway" option from the AWS console.


-Select "Cached Gateway" from the options when you start


-Select "Cache Volume" inside the gateway.


-CHAP has to be fully configured. It is fully supported though.

Please note I had to configure both secret and not secret auth for the configuration to work.  YMMV

S2D Options For Windows 2016:
Here are a few items I had to do with S2D on Windows 2016.  Note the hypervisor in this case is Azure but same concept applies:

-These are the S2D requirements for us, read the docs for your environment.


-This tripped me up, be sure to find and use the 'Friendly Name'. 


-You can verify it now


-Verify your steps on Node 2 and after this you will pass validation in WSFC.