FortiGate Autoscale for GCP features

Major components

• The Instance group. The Instance group contains one to many FortiGate-VMs (PAYG licensing model). This Instance group will dynamically scale out or scale in based on cpu_utilization.
• The configset folder contains files that are loaded as the initial configuration for a new FortiGate-VM instance.
  • baseconfig is the base configuration. This file can be modified as needed to meet your network requirements. Placeholders such as {SYNC_INTERFACE} are explained in the section Configset placeholders.
• Tables in Firestore. These tables are required to store information such as health check monitoring, primary election, state transitions, etc. These records should not be modified unless required for troubleshooting purposes.

Configset placeholders

When the FortiGate-VM requests the configuration from the Auto Scaling function, the placeholders in the table below will be replaced with associated environment variables stored in Cloud Functions.

Placeholder	Type	Description
{SYNC_INTERFACE}	Text	The interface for FortiGate-VMs to synchronize information. All characters must be lowercase.
{CALLBACK_URL}	URL	The Cloud Functions URL to interact with the Auto Scaling handler script. Automatically generated during the Terraform deployment.
{PSK_SECRET}	Text	The Pre-Shared key used in FortiOS. Randomly generated during the Terraform deployment. Changes to the PSK secret after FortiGate Autoscale for GCP has been deployed are not reflected here. For new instances to be spawned with the changed PSK secret, this environment variable will need to be manually updated.
{ADMIN_PORT}	Number	A port number specified for administration login. A positive integer such as 443 etc. Default value: 8443. Changes to the admin port after deployment are not reflected here. For new instances to be spawned with the changed admin port, this environment variable will need to be updated.