Deploying and configuring FortiGate A-P HA
FortiGate supports A-P HA on AWS, with two FortiGate instances synchronizing configuration and sessions with FortiOS 6.0. This FortiGate native mechanism achieves HA without using AWS clustering/balancing technologies. One instance runs as the primary/master, while the other runs as the secondary/slave (hereafter referred to as “primary”/”FortiGate A” and “secondary”/”FortiGate B”, respectively). When the primary fails to operate, the secondary automatically promotes itself to the primary. See Reviewing the network failover diagram.
This deployment is a single AZ solution.
To deploy this HA, you generally do not subscribe FortiGate EC2 instances from the AWS marketplace portal. Instead, you kick off deployment using CFTs.
See below for FortiGate product listings on AWS: