Fortinet black logo

SD-WAN Architecture for Enterprise

7.2.0

Cloud design considerations

Cloud design considerations

FortiGate VMs can be deployed as SD-WAN gateways for all major public and private cloud providers, including AWS, Azure, GCP, Oracle and AliCloud. While every cloud environment may differ, there are two fundamental ways a FortiGate VM is typically used:

  • Static environments: the FortiGate VM will be assigned a traditional, static IP that does not change, and is expected to provide the head-end connectivity to the cloud workload.
  • Dynamic environments: services or deployments where the FortiGate VM is expected to change, and/or the FortiGate VM is never the same.

The type of cloud design used will depend on the environment in which the FortiGate VM is deployed.

This section contains the following topics:

Cloud design considerations

FortiGate VMs can be deployed as SD-WAN gateways for all major public and private cloud providers, including AWS, Azure, GCP, Oracle and AliCloud. While every cloud environment may differ, there are two fundamental ways a FortiGate VM is typically used:

  • Static environments: the FortiGate VM will be assigned a traditional, static IP that does not change, and is expected to provide the head-end connectivity to the cloud workload.
  • Dynamic environments: services or deployments where the FortiGate VM is expected to change, and/or the FortiGate VM is never the same.

The type of cloud design used will depend on the environment in which the FortiGate VM is deployed.

This section contains the following topics: