This whitepaper demonstrates using various services on AWS to deploy Microsoft Windows Server 2012 R2 as a Network Address Translation (NAT) device and deploy the Microsoft DirectAccess Windows Server role. Tools such as AWS Toolkit for Microsoft Visual Studio and AWS Toolkit for Windows PowerShell are used to automate the deployments. The target audience is IT infrastructure administrators and developer operations personnel. When completed, the network will have the following configuration capabilities:
- A simulated corporate network with a DMZ. This Virtual Private Cloud (VPC) will have a private and public subnet leveraging a dual-homed Windows Server as a NAT device and Remote Desktop Gateway device. This connects the private subnet to the public subnet.
- The NAT device will also function as a reverse proxy, publishing ports 80 and 443 on the private subnet.
- A domain controller that has been configured with Certificate Services to support DirectAccess.
- A Windows Remote Access server with DirectAccess configured using its Single NIC Topology.
- A simulated remote network featuring a Windows client in a separate VPC. This client VPC could be located in a separate region and could use the Internet to communicate to the primary VPC.
- The remote client will be joined to the corporate networking leveraging the Windows Offline Domain Join capability.
- DirectAccess will be enabled so the remote client has complete connectivity to the corporate private network.
Read the Microsoft DirectAccess on AWS Whitepaper
Are you interested in running Microsoft Windows Server or Windows Server applications, such as SQL or SharePoint, on AWS and would like to have an AWS Sales Representative follow-up with you about your IT project?
Please register below and an AWS Sales Representative will contact you. An asterisk (*) indicates required information.
Questions about Licensing? See our Microsoft License Mobility page.