reference deployment

Microsoft servers on AWS

Deploy SharePoint, SQL Server, Exchange, Lync, WAP & AD FS with a single click

Amazon Web Services (AWS) provides a suite of infrastructure services that help you deploy Microsoft workloads for your test or production use on AWS. This Quick Start deploys five business productivity servers from Microsoft — SharePoint Server, Lync Server, Exchange Server, SQL Server, and Web Application Proxy with Active Directory Federation Services (AD FS) — in a single step, in a highly available Multi-AZ architecture on AWS.

By deploying this Quick Start, you can take advantage of the email, collaboration, communications, and directory features provided by the Microsoft servers along with the flexibility and security of AWS. The advantages of running Microsoft servers on AWS include add-on compatibility, scalability, agility, cost, optimization, reliability, and high availability.

You can also deploy these Microsoft servers separately from the Quick Start catalog.

AWS-Logo_Full-Color_100x60

This Quick Start was developed by
AWS solutions architects.

  •  What you'll build
  •  How to deploy
  •  Cost and licenses
  •  What you'll build
  • This Quick Start uses AWS CloudFormation templates to set up the following  environment on AWS:

    • A virtual private cloud (VPC) to provide a private, isolated section of the AWS Cloud for your servers and services.
    • Use of two Availability Zones for high availability and disaster recovery.
    • Microsoft Windows Server 2012 R2 with Active Directory Domain Services (AD DS) for user authentication and authorization, and Remote Desktop Gateway (RD Gateway) for remote Windows administration.
    • Network address translation (NAT) gateways deployed to public subnets to provide outbound internet access for instances in the private subnets.
    • SQL Server 2012 or 2014 instances configured in a Windows Server Failover Cluster (WSFC) for database services.
    • Paired Lync Server 2013 Standard Edition front-end servers and (optionally) two edge servers.
    • Exchange Server 2013 environment that supports 250 mailboxes; this includes two multi-role servers with mailbox and client access server (CAS) roles, and (optionally) two edge transport servers.
    • SharePoint Server 2016 farm with two web front-end servers and two application servers based on a traditional or streamlined topology.
    • Web Application Proxy with AD FS servers.
  •  How to deploy
  • To deploy Microsoft servers on AWS, follow the instructions in the deployment guide. The deployment process includes these steps:

    1. If you don't already have an AWS account, sign up at https://aws.amazon.com.
    2. Launch the Quick Start into your AWS account and customize its configuration. The deployment takes 3-4 hours.
    3. Test the servers on AWS, and create users and content.

    To customize your deployment, you can choose a traditional or streamlined topology for your SharePoint Server farm, include Office Online Servers, include edge servers for Lync and Exchange, and choose the version of SQL Server to deploy.

  •  Cost and licenses
  • You are responsible for the cost of the AWS services used while running this Quick Start reference deployment. The cost will depend on your Quick Start deployment configuration. There is no additional cost for using the Quick Start.

    The Quick Start launches the Amazon Machine Image (AMI) for Windows Server 2012 R2 and includes the license for the Windows Server 2012 R2 operating system.

    By default, this Quick Start installs the free trial versions of the Microsoft business productivity servers. To use these servers beyond the trial period, you must obtain licenses from Microsoft. For production environments, you can license Microsoft server products through the Microsoft License Mobility through Software Assurance program, and provide your own product key after deployment. For development and test environments, you can leverage your existing MSDN licenses using Amazon EC2 Dedicated Instances or Dedicated Hosts. For details, see the MSDN on AWS webpage.