Predeployment steps
To complete predeployment steps:
- Decide the region, zones, licensing, firmware version, and machine type for the deployment.
- Prepare three virtual private cloud (VPC) networks with non-overlapping subnets in the deployment region to use as external, internal, and heartbeat networks. You can optionally split the heartbeat and dedicated management network. This is obligatory for older firmware.
- If desired, complete the following predeployment table. This allows you to easily access necessary information during the deployment. Mentions of these fields are bolded in subsequent sections of this guide:
REGION
Region to deploy to. It should be the same region your servers are using.
ZONE_1
Primary availability zone (AZ). This zone must be in REGION.
ZONE_2
Secondary AZ. This zone must be in REGION.
VPC_EXT/SUBNET_EXT
External VPC and subnet names.
VPC_INT/SUBNET_INT
Internal VPC and subnet names.
VPC_HASYNC / SUBNET_HASYNC
Heartbeat and management VPC and subnet names.
FIRMWARE_VERSION
Firmware version you plan to deploy. Some versions may be unavailable.
LICENSING
Bring your own license and pay as you go licensing use different images. You cannot change licensing without redeploying the FortiGates.
MACHINE_TYPE
Select the machine type that matches your performance requirements with a minimum of three vCPUs.