You can deploy FortiGate-VM to support Auto Scaling on AWS. This requires a manual deployment incorporating CloudFormation Templates (CFT).
Multiple FortiGate instances can form an Auto Scaling group to provide highly efficient clustering at times of high workloads. FortiGate instances can be scaled out automatically according to predefined workload levels. When a spike in traffic occurs, the Lambda script is invoked to scale out the group by automatically adding FortiGate instances. Auto Scaling is achieved by using FortiGate-native high availability features such as Config-Sync, which synchronizes operating system configurations across multiple FortiGate instances at the time of scale-out events.
This Auto Scaling feature is available with FortiOS 6.0.3 and later versions for On-Demand (PAYG) instances. BYOL instance support is planned for a later time.
Before you deploy FortiGate Auto Scaling on AWS, it is recommended that you become familiar with the following AWS services. If you are new to AWS, see Getting Started with AWS.
- Amazon Elastic Cloud Compute (Amazon EC2)
- Amazon EC2 Auto Scaling
- Amazon VPC
- AWS CloudFormation
- AWS Lambda
- Amazon DynamoDB
- Amazon API Gateway
- Amazon CloudWatch
- Amazon S3
It is expected that Auto Scaling will be deployed by DevOps engineers or advanced system administrators who are familiar with the area.
FortiGate Auto Scaling uses AWS CFT to set up the following:
- A highly available architecture that spans two Availability Zones
- A virtual private cloud (VPC) configured with public and private subnets according to AWS best practices, to provide you with your own virtual network on AWS
- An Internet gateway to allow access to the Internet
- In the public subnets, FortiGates that act as NAT gateways, allowing outbound Internet access for resources in the private subnets
- In the public subnets, a FortiGate host in an Auto Scaling group compliments AWS security groups to provide intrusion protection, web filtering, and threat detection to protect your services from cyber attacks. It also allows VPN access by authorized users.
- An externally facing network load balancer is created as part of the deployment process. An internally facing network load balancer is optional.
- Amazon API Gateway, which acts as a front door by providing a callback URL for the FortiGate Auto Scaling group. FortiGates use API Gateway to send API calls and to process FortiGate Config-Sync tasks to synchronize OS configuration across multiple FortiGate instances at the time of the Auto Scaling scale-out event. This is currently only for internal use. There is no public access available.
- AWS Lambda, which allows you to run certain scripts and code without provisioning servers. Fortinet provides Lambda scripts for running Auto Scaling. Lambda functions are used to handle Auto Scaling, failover management, AWS CloudFormation deployment, and configuration for other related components.
- An Amazon DynamoDB database that uses Fortinet-provided scripts to store information about Auto Scaling condition states.