When the active peer goes down, the passive peer detects
this failure and becomes active. Additionally, it triggers API calls
to the AWS infrastructure to move the configured secondary IP addresses
from the dataplane interfaces of the failed peer to itself. Additionally,
AWS updates the route tables to ensure that traffic is directed
to the active firewall instance. These two operations ensure that
inbound and outbound traffic sessions are restored after failover.
This option allows you to take advantage of DPDK to improve the
performance of your VM-Series firewall instances and provides better
failover time than interface-move HA, while supporting all the features
provided by interface-move.