Product Pillars
Network Security
Network Security
NOC & SOC Management
Enterprise Networking
Business Communications
Zero Trust Access
ZTNA
SASE
Identity
Cloud Security
Hybrid Cloud Security
Cloud Native Protection
Web Application / API Protection
SAAS Security
Security Operations
SOC Platform
Advanced Threat Protection
Endpoint Security
Best Practices
Solution Hubs
Curated links by solution
Cloud
Popular Solutions
4-D Resources
Define, Design, Deploy, Demo
Hardware Guides
Product A-Z

Version:

6.0.0

Table of Contents

Use Case: High Availability for FortiGate on AWS

6.0.0
6.0.0
Copy Link

Deploying the Windows Server

  1. Connect to AWS and go to Network Interfaces. Right-click the private network interface, select Change Source/Dest Check, and select Disable. AWS now lets packets pass through instead of filtering them.
  2. Go to EC2 instances and select Launch Instance.
  3. Configure, then launch the instance:
    1. Select t2.micro for the instance type and select Next: Configure Instance Details.
    2. Set Network to Fortinet-VPC, Subnet to Application Subnet 1, and Network Interfaces to eth0. Select Next: Add Storage.
    3. If necessary, change your storage option.
    4. Select Next: Tag Instance. Enter a Name tag, then select Next: Configure Security Group.
    5. Enable Select an existing security group and select the Allow everything group.
    6. Select Review and Launch.
    7. After you have reviewed the configuration, select the Fortinet-AWS-Keypair that you previously created.
    8. Review the information, then select Launch Instance to deploy the server.
  4. Go to EC2 instance and select the new subnet. Select Get Windows Password.
  5. Click Key Pair Path Browse and select the key pair file created earlier.
  6. Select Decrypt Password to receive the administrator password for RDP connection.
  7. Test the connection to your RDP server using your terminal and the following command:

    C:\> mstsc /v: /admin

Deploying the Windows Server

  1. Connect to AWS and go to Network Interfaces. Right-click the private network interface, select Change Source/Dest Check, and select Disable. AWS now lets packets pass through instead of filtering them.
  2. Go to EC2 instances and select Launch Instance.
  3. Configure, then launch the instance:
    1. Select t2.micro for the instance type and select Next: Configure Instance Details.
    2. Set Network to Fortinet-VPC, Subnet to Application Subnet 1, and Network Interfaces to eth0. Select Next: Add Storage.
    3. If necessary, change your storage option.
    4. Select Next: Tag Instance. Enter a Name tag, then select Next: Configure Security Group.
    5. Enable Select an existing security group and select the Allow everything group.
    6. Select Review and Launch.
    7. After you have reviewed the configuration, select the Fortinet-AWS-Keypair that you previously created.
    8. Review the information, then select Launch Instance to deploy the server.
  4. Go to EC2 instance and select the new subnet. Select Get Windows Password.
  5. Click Key Pair Path Browse and select the key pair file created earlier.
  6. Select Decrypt Password to receive the administrator password for RDP connection.
  7. Test the connection to your RDP server using your terminal and the following command:

    C:\> mstsc /v: /admin