Deploy Exchange Server 2016 into an existing VPC


I would like to deploy two exchange servers in AWS into an existing VPC using the cloud formation template provided in GitHub. I do have an existing active directory instance, but the template in GitHub includes active directory deployment. I want to isolate that part of the template only to include exchange server deployment. Is this possible and do I need to store the required PowerShell scripts and cmdlets in a new S3 bucket?

1 Answer

You can certainly just use the parts of the template that are relevant for your environment. That will mainly be removing the AD components from the template and setting the parameters to your existing AD values. Be sure to update any Ref functions that refer to AD resources to what your actual values are as well, if present. You do not need to store the PS scripts in a new bucket, the default used by the Quickstart is public.

Edit: If this is for purposes of testing and experimenting, then no problem with what you are doing. For a production deployment, you may want to deploy an independent AD forest for Exchange, sometimes called a "resource forest". This article is for 2013, but the same concepts apply.

answered 2 years ago
reviewed 2 years ago
  • Hi Mike, Thanks for your response above. This is for testing first but the goal is to eventually deploy this in production. We already have 2 exchange servers in AWS, which were deployed manually and without an independent AD forest (only our existing AD forest). I want to deploy this using the quickstart template and possibly create a service catalog product that can be consumed in the future. Is the independent AD forest a requirement if I use the quickstart template?

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions