Fortinet Document Library

Version:


Table of Contents

AliCloud Administration Guide

6.4.0
Download PDF
Copy Link

FortiGate Autoscale for AliCloud features

Major components

  • The Auto Scaling group. The Auto Scaling group contains one to many FortiGate-VMs (PAYG licensing model). This Auto Scaling group will dynamically scale-out or scale-in based on the scaling metrics specified in the scaling rules.
  • 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 Configset placeholders table below.
  • Tables in TableStore. 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 Function Compute.

Placeholder

Type

Description

{SYNC_INTERFACE}

Text

The interface for FortiGate-VMs to synchronize information.

All characters must be lowercase.

{CALLBACK_URL}

URL

The endpoint 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.

Note

Changes to the PSK secret after FortiGate Autoscale for AliCloud 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.

Note

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.

FortiGate Autoscale for AliCloud features

Major components

  • The Auto Scaling group. The Auto Scaling group contains one to many FortiGate-VMs (PAYG licensing model). This Auto Scaling group will dynamically scale-out or scale-in based on the scaling metrics specified in the scaling rules.
  • 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 Configset placeholders table below.
  • Tables in TableStore. 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 Function Compute.

Placeholder

Type

Description

{SYNC_INTERFACE}

Text

The interface for FortiGate-VMs to synchronize information.

All characters must be lowercase.

{CALLBACK_URL}

URL

The endpoint 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.

Note

Changes to the PSK secret after FortiGate Autoscale for AliCloud 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.

Note

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.