Microsoft SharePoint Server 2016 on the AWS Cloud: Quick Start Reference Deployment
Deployment Guide
AWS Quick Start team
August 2014 (last update: March 2018)
This Quick Start reference deployment includes architectural considerations and configuration steps for building a Microsoft SharePoint Server 2016 environment on the Amazon Web Services (AWS) Cloud. It also provides links for viewing and launching AWS CloudFormation templates that automate the deployment.
This guide is for IT infrastructure architects, administrators, and DevOps professionals who are planning to implement or extend SharePoint Server 2016 on the AWS Cloud. The guide requires basic familiarity with SharePoint Server architecture and management. For more information about SharePoint Server, including general guidance and best practices, consult the Microsoft SharePoint product documentation.
The following links are for your convenience. Before you launch the Quick Start, please review the architecture, configuration, network security, and other considerations discussed in this guide.
-
If you have an AWS account and you’re already familiar with AWS services and SharePoint, you can launch the Quick Start to build the architecture shown in Figure 2 in a new virtual private cloud (VPC). The deployment takes approximately three hours. If you’re new to AWS or to this SharePoint Quick Start, please review the implementation details and follow the step-by-step instructions provided later in this guide.
-
If you want to take a look under the covers, you can view the AWS CloudFormation template that automates the deployment.
Note
You are responsible for the costs related to your use of any AWS services used while running this Quick Start reference deployment. Prices are subject to change. For more information, see the Cost and Licenses section.
About Quick Starts
Quick Starts are automated reference deployments for key workloads on the AWS Cloud. Each Quick Start launches, configures, and runs the AWS compute, network, storage, and other services required to deploy a specific workload on AWS, using AWS best practices for security and availability.
