Components (deployment on Windows) - Amazon Launch Wizard
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Components (deployment on Windows)

A SQL Server application deployed on Windows with Launch Wizard includes the following components:

  • A virtual private cloud (VPC) configured with public and private subnets across two Availability Zones. A public subnet is a subnet whose traffic is routed to an internet gateway. If a subnet does not have a route to the internet gateway, then it is a private subnet. The VPC provides the network infrastructure for your SQL Server deployment. You can choose an optional third Availability Zone for additional SQL cluster nodes, as shown below.

  • An internet gateway to provide access to the internet.

  • In the public subnets, Windows Server-based Remote Desktop Gateway (RDGW) instances and network address translation (NAT) gateways for outbound internet access. If you are deploying in your preexisting VPC, Launch Wizard uses the existing NAT gateway in your VPC. For more information about NAT gateways, see NAT Gateways.

  • Elastic IP addresses associated with the NAT gateway and RDGW instances. For more information about Elastic IP addresses, see Elastic IP Addresses.

  • In the private subnets, Active Directory domain controllers.

  • In the private subnets, Windows Server-based instances as Windows Server Failover Clustering (WSFC) nodes. For more information, see Windows Server Failover Clustering with SQL Server.

  • SQL Server Enterprise edition with SQL Server Always On Availability Groups on each WSFC node. This architecture provides redundant databases and a witness server to ensure that a quorum can vote for the node to be promoted to the controlling resource. The default architecture mirrors an on-premises architecture of two SQL Server instances spanning two subnets placed in two different Availability Zones. For more information about SQL Server Always On Availability Groups, see Overview of Always On Availability Groups (SQL Server).

  • Security groups to ensure the secure flow of traffic between the instances deployed in the VPC. For more information, see Security Groups for Your VPC.

    Note

    If you choose to deploy SQL Server Always On through Launch Wizard into your existing VPC, there is an additional mandatory check box on the console to indicate whether VPC and public/private subnet requirements have been met.

  • Amazon FSx to provide highly available and redundant storage across Availability Zones for clustering.

    Note

    Launch Wizard uses two Availability Zones.

You can build a SQL HA installation, as shown in the following diagram.

Deploy SQL Server HA with Launch Wizard

You can also choose to build an architecture with SQL Server Always On FCI, as shown in the following diagram.

Deploy SQL Server Always On FCI