Fortinet Document Library

Version:


Table of Contents

About FortiGate for AWS

Deploying FortiGate on AWS

Deploying auto scaling on AWS

Single FortiGate-VM Deployment

Use Case: High Availability for FortiGate on AWS

Security Fabric Connector Integration with AWS

Resources

Upgrade Path Tool
6.0.0
Copy Link

ELB-based HA/load-balancing

See Deploying and configuring ELB-based HA/load balancing.

FortiGate can achieve HA using AWS ELB load-balancing. Two FortiGates can be deployed and associated with an ELB, and traffic is balanced between the two. If one FortiGate fails, the other handles traffic. External and internal ELBs are required if you want to serve both incoming and outgoing traffic for protected VMs.

Multiple AZs can be protected and turned high available depending on how you design the topology.

You can also combine AWS Route 53 to use DNS name together with ELB.

Resources

ELB-based HA/load-balancing

See Deploying and configuring ELB-based HA/load balancing.

FortiGate can achieve HA using AWS ELB load-balancing. Two FortiGates can be deployed and associated with an ELB, and traffic is balanced between the two. If one FortiGate fails, the other handles traffic. External and internal ELBs are required if you want to serve both incoming and outgoing traffic for protected VMs.

Multiple AZs can be protected and turned high available depending on how you design the topology.

You can also combine AWS Route 53 to use DNS name together with ELB.