Created on
07-27-2025
09:35 PM
Edited on
07-28-2025
05:46 AM
By
Matt_L
Description | This article describes how to guarantee that all elastic IP addresses (primary and secondary) migrate correctly when a failover is performed on a FortiGate cluster in AWS. |
Scope | FortiGate. |
Solution |
| | Solution | Pros | Cons |
|---|---------------------------------|----------------------------------------------|-------------------------------------------|
| 1 | SDN Connector | • Fortinet‑native, no extra services | • Requires FortiOS ≥6.4 |
| | | • Moves EIPs and routes automatically | • Needs IAM role with broad perms |
Prerequisites
"Describe*", "AssociateAddress", "DisassociateAddress", "ModifyNetworkInterfaceAttribute", "CreateRoute", "ReplaceRoute", "AssignPrivateIpAddresses", "UnassignPrivateIpAddresses", "DescribeCluster", "ListClusters", "BatchGetResourceConfig".
Step‑by‑Step:
get system status | grep Version
config system sdn-connector
edit "aws-ha"
set type was
set use-metadata-iam enable <----- Rely on instance profile.
set update-interval 30 <----- Poll every 30 s.
set update-elastic-ip enable <----- Move ALL EIPs.
set update-route enable <----- Flip routes to new ENI.
next
end
diagnose sys sdn-connector list
Ensure all ENIs (Elastic Network Interface) and EIPs (Elastic IP Address) appear.
config system ha
set unicast-hb enable
set standalone-config-sync disable
end
diagnose system ha reset‑uptime.
config system sdn-connector
edit "aws-ha"
set update-elastic-ip disable
set update-route disable
next
end
"aws ec2 associate-address --allocation-id eipalloc-xxxx --network-interface-id eni-yyyy"
Related articles:
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.