Deployment options - AWS Launch Wizard

Deployment options

AWS Launch Wizard provides the following deployment paths:

Deployment on Windows

  1. Deploy SQL Server into a new VPC across multiple Availability Zones.

    When you choose this configuration option, Launch Wizard builds a new AWS environment consisting of the VPC, subnets, NAT gateways, security groups, domain controllers, and other infrastructure components. It then deploys Windows Server Failover Clustering (WSFC) with SQL Server across multiple Availability Zones into the new VPC.

  2. Deploy SQL Server into a new VPC on a single node.

    When you choose this configuration option, Launch Wizard builds a new AWS environment consisting of the VPC, subnet, NAT gateway, security groups, domain controllers, and other infrastructure components. It then deploys SQL Server on a single node into the new VPC.

  3. Deploy SQL Server into an existing VPC and create a new AWS Managed Active Directory.

    When you choose this configuration option, Launch Wizard builds a new AWS environment that consists of security groups, domain controllers, and other infrastructure components, and then deploys Windows Server Failover Clustering (WSFC) with SQL Server into the specified VPC and subnets. Your AWS environment must include a VPC with two or three Availability Zones, private subnets in each Availability Zone, and at least one public subnet in the VPC. Launch Wizard supports only AWS Managed Microsoft Active Directory for this scenario.

  4. Deploy SQL Server into an existing VPC with an existing AWS Managed Active Directory across multiple Availability Zones.

    When you choose this configuration option, Launch Wizard provisions Windows Server Failover Clustering (WSFC) across multiple Availability Zones in your existing AWS infrastructure. Your AWS environment must include a VPC with two or three Availability Zones, private subnets in each Availability Zone, at least one public subnet in the VPC, and an AWS Active Directory in the VPC (this is the Active Directory on which you deploy your SQL nodes).

  5. Deploy SQL Server into an existing VPC with an existing AWS Managed Active Directory on a single node.

    When you choose this configuration option, Launch Wizard provisions SQL Server on a single node in your existing AWS infrastructure. Your AWS environment must include a VPC in one Availability Zone, a private subnet, a public subnet in the VPC, and an AWS Active Directory in the VPC (this is the Active Directory on which you deploy your SQL nodes).

  6. Deploy SQL Server into an existing VPC across multiple Availability Zones and connect to a self-managed Active Directory.

    When you choose this configuration option, Launch Wizard provisions Windows Server Failover Clustering (WSFC) across multiple Availability Zones in your existing AWS infrastructure. Your AWS environment must include a VPC with two or three Availability Zones, private subnets in each Availability Zone, and at least one public subnet in the VPC. If your self-managed Active Directory resides in a different network, you must also establish connectivity and configure DNS resolution from your VPC to the self-managed Active Directory's network. For more information, see Self-managed Active Directory.

  7. Deploy a SQL Server into an existing VPC on a single node and connect to a self-managed Active Directory.

    When you choose this configuration option, Launch Wizard provisions SQL Server on a single node in your existing AWS infrastructure. Your AWS environment must include a VPC in one Availability Zone, a private subnet, and a public subnet in the VPC. If your self-managed Active Directory resides in a different network, you must also establish connectivity and configure DNS resolution from your VPC to the self-managed Active Directory's network. For more information, see Self-managed Active Directory.

  8. Deploy SQL HA on Dedicated Hosts with your Windows BYOL or SQL Server BYOL licensed AMIs.

    When you choose this configuration option, Launch Wizard provisions SQL Server Always On Availability Groups on your existing Dedicated Hosts using your existing SQL Server licenses (BYOL) for deploying SQL Server High Availability solutions.

You can configure additional settings, such as the SQL Server version (by your choice of AMI), in addition to instance types and Amazon EBS volume types based on the infrastructure requirements that you specify.

Deployment on Linux

  1. Deploy SQL Server into a new VPC across multiple Availability Zones.

    When you choose this configuration option, Launch Wizard builds a new AWS environment consisting of the VPC, subnets, NAT gateways, security groups, and other infrastructure components. It then deploys SQL Server Always On Availability Groups (AG) across multiple Availability Zones into the VPC using Pacemaker and fencing agents for cluster management.

  2. Deploy SQL Server into a new VPC on a single node.

    When you choose this configuration option, Launch Wizard builds a new AWS environment consisting of the VPC, subnet, NAT gateways, security groups, and other infrastructure components. It then deploys SQL Server AG on a single node into the VPC using Pacemaker and fencing agents for cluster management.

  3. Deploy SQL Server into an existing VPC across mulitple Availability Zones.

    When you choose this configuration option, Launch Wizard builds a new AWS environment that consists of security groups and other infrastructure components, and then deploys SQL Server AG across multiple Availability Zones into the specified VPC and subnets. Your AWS environment must include a VPC with three Availability Zones, private subnets in each Availability Zone, and at least one public subnet in the VPC.

  4. Deploy SQL Server into an existing VPC on a single node.

    When you choose this configuration option, Launch Wizard builds a new AWS environment that consists of security groups and other infrastructure components, and then deploys SQL Server AG on a single node into the specified VPC and subnet. Your AWS environment must include a VPC with one Availability Zone, a private subnet, and a public subnet in the VPC.