[Use case] Set up a Windows Server in the protected network

This recipe is part of the process of deploying FortiGate for AWS. See below for the rest of the recipes in this process:

1. Determine your licensing model
2. Register and download your licenses
3. Create a VPC and subnets
4. Attach the new VPC to the Internet gateway
5. Subscribe to the FortiGate
6. Create a routing table and associate subnets
7. Connect to the FortiGate
8. [Use case] Set up a Windows Server in the protected network
9. [Connectivity test] Configure FortiGate firewall policies and virtual IPs

1. In the AWS Management Console, select EC2. Select Launch Instance, then select the Microsoft Windows Server 2012 R2 that applies to your environment. You will use this to test connectivity with Remote Desktop access.

2. In the Configure Instance Details step, in the Network field, select the VPC of the FortiGate. In the Subnet field, select the private subnet.

3. In the Configure Security Group step, configure a security group for the Windows server so that it allows Internet access. In this example, we use Remote Desktop TCP port 3389, and other ports are optional. Select Review and Launch.

4. Select a key pair, select the acknowledgement check box, and select Launch Instances.

The post [Use case] Set up a Windows Server in the protected network appeared first on Fortinet Cookbook.