Deploying a FortiGate-VM on a T2A instance

FortiOS 7.2.4 and later versions support the GCP T2A instance family. A publicly available image has been created. You can use it to create a FortiGate-VM instance via the GCloud CLI, leveraging the ARM-based CPU instance family T2A. See Expanding the Tau VM family with Arm-based processors.

To deploy a FortiGate-VM on GCP with the T2A family instance:

The example uses GCloud shell or Linux variables. Edit the variables to match your project ID, zone, and service account:

project=<GCP project ID>

zone=us-central1-a

serviceaccount=<your designated services account>

image=projects/fortigcp-project-001/global/images/fortinet-fgt-arm64-724-20230216-001-w-license

Do not edit the image variable as this specifies the ARM specific image.

The following commands deploy a FortiGate-VM on a T2A instance type with two network adapters. The networks and subnets referenced in the GCloud SDK command must be in place and/or created prior to running the command. Edit the following command to fit your environment:

gcloud compute instances create fortigate-arm-t2a \ 
  --project=$project \ 
  --zone=$zone \ 
  --machine-type=t2a-standard-2 \ 
  --network-interface=private-network-ip=10.0.1.11,nic-type=GVNIC,subnet=unprotected-public-subnet \ 
  --network-interface=private-network-ip=10.0.2.11,nic-type=GVNIC,subnet=protected-private-subnet,no-address \ 
  --can-ip-forward \ 
  --service-account=$serviceaccount \ 
  --scopes=https://www.googleapis.com/auth/cloud-platform \ 
  --create-disk=auto-delete=yes,boot=yes,device-name=fortigate-arm-t2a,image=$image,mode=rw,size=10,type=projects/$project/zones/$zone/diskTypes/pd-balanced \ 
  --create-disk=auto-delete=yes,device-name=fortigate-arm-t2a-log,mode=rw,name=fortigate-arm-t2a-log,size=10,type=projects/$project/zones/$zone/diskTypes/pd-balanced

The following shows the GCloud CLI output when the deployment succeeds:

The following shows the FortiGate-VM bring your own license instance details on the GCP portal: