Exchange Server on AWS
Exchange Server Quick Start

Microsoft Exchange Server 2013 on the AWS Cloud: Quick Start Reference Deployment

Deployment Guide

AWS Quick Start team

January 2015  (last update: March 2018)

This Quick Start reference deployment guide discusses architectural considerations and configurations used to build a Microsoft Exchange Server 2013 environment on the Amazon Web Services (AWS) cloud. It also provides links for viewing and launching AWS CloudFormation templates that automate the deployment.

The guide targets IT infrastructure architects, administrators, and DevOps personnel. After reading it, you should have a good understanding of how to launch the necessary infrastructure to support Exchange Server 2013 on the AWS cloud.

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 Microsoft Exchange and AWS, you can launch the Quick Start to deploy Exchange Server 2013 with Active Directory Domain Services (AD DS) into a new Amazon VPC in your AWS account. The deployment takes approximately 3 hours. (To deploy Exchange Server into an existing Amazon VPC, see the Automated Deployment section.)



  • If you'd like to take a look under the covers, you can view the template to see the AWS CloudFormation script that automates this deployment. You can customize the template during launch, or download and extend it for other projects.



You are responsible for the costs related to your use of any AWS services used while running this Quick Start reference deployment. See the pricing pages of the AWS services you will be using for full details.

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.

On this page: