The ResourceGroup Tag Key used on all resources and as the name prefix of all applicable resources. Can only contain uppercase letters, lowercase letters, and numbers, ampersat(@), hyphens (-), period (.), and hash (#).

Maximum length is 50.

The list of AZs to use for the subnets in the VPC. The FortiGate Autoscale solution uses two AZs from your list and preserves the logical order you specify.

The Classless Inter-Domain Routing (CIDR) block for the FortiGate Autoscale VPC.

The CIDR block for the subnet located in AZ 1 where the FortiGate Autoscale instances will be deployed to.

The CIDR block for the subnet located in AZ 2 where the FortiGate Autoscale instances will be deployed to.

The CIDR block for the private subnet located in AZ 1 where it is protected by the FortiGates in the public subnet of the same AZ.

The ID of the existing VPC where FortiGate Autoscale will be deployed. The VPC must have the option DNS hostnames enabled and each of the two AZs in the VPC must have at least 1 public subnet and at least 1 private subnet.

The CIDR block of the selected existing VPC. This can be found in parentheses in the VPC ID parameter selection.

The ID of the public subnet 1 located in AZ 1 of the selected existing VPC.

The ID of the public subnet 2 located in AZ 2 of the selected existing VPC.

The ID of the private subnet 1 located in AZ 1 of the selected existing VPC. This subnet will be protected by the FortiGates in the public subnet of the same AZ.

The ID of the private subnet 2 located in AZ 2 of the selected existing VPC. This subnet will be protected by the FortiGates in the public subnet of the same AZ.

Instance type to launch for the FortiGate-VMs in the Auto Scaling group. There are t2.small and compute-optimized instances such as c4 and c5 available with different vCPU sizes and bandwidths. For more information about instance types, see Instance Types.

FortiOS version supported by FortiGate Autoscale for AWS.

A secret key for the FortiGate-VM instances to securely communicate with each other. Must contain numbers and letters and may contain special characters.

Maximum length is 128.

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

A port number for FortiGate-VM administration.

Do not use the FortiGate reserved ports 443, 541, 514, or 703.

Minimum is 1. Maximum is 65535.

CIDR block for external admin management access.

0.0.0.0/0 accepts connections from any IP address. We recommend that you use a constrained CIDR range to reduce the potential of inbound attacks from unknown IP addresses.

The number of FortiGate-VM instances the BYOL Auto Scaling group should have at any time.

For High Availability in BYOL-only and Hybrid use cases, ensure at least 2 FortiGate-VMs are in the group.

For specific use cases, set to 0 for On-Demand-only, and >= 2 for BYOL-only or hybrid licensing.

Minimum number of FortiGate-VM instances in the BYOL Auto Scaling group.

For specific use cases, set to 0 for On-Demand-only, and >= 2 for BYOL-only or hybrid licensing.

For BYOL-only and hybrid licensing deployments, this parameter must be at least 2. If it is set to 1 and the instance fails to work, the current FortiGate-VM configuration will be lost.

Maximum number of FortiGate-VM instances in the BYOL Auto Scaling group.

For specific use cases, set to 0 for On-Demand-only, and >= 2 for BYOL-only or hybrid licensing. This number must be greater than or equal to the Minimum group size (BYOL).

The number of FortiGate-VM instances the On-Demand Auto Scaling group should have at any time.

For High Availability in an On-Demand-only use case, ensure at least 2 FortiGate-VMs are in the group.

For specific use cases, set to 0 for BYOL-only, >= 2 for On-Demand-only, and >= 0 for hybrid licensing.

Minimum number of FortiGate-VM instances in the On-Demand Auto Scaling group.

For specific use cases, set to 0 for BYOL-only, >= 2 for On-Demand-only, and >= 0 for hybrid licensing.

For On-Demand-only deployments, this parameter must be at least 2. If it is set to 1 and the instance fails to work, the current FortiGate-VM configuration will be lost.

Maximum number of FortiGate-VM instances in the On-Demand Auto Scaling group.

For specific use cases, set to 0 for BYOL-only, >= 2 for On-Demand-only, and >= 0 for hybrid licensing. This number must be greater than or equal to the Minimum group size (On-Demand instances).

The threshold (in percentage) for the FortiGate-VM Auto Scaling group to scale out (add) 1 instance.

Minimum is 1. Maximum is 100.

The threshold (in percentage) for the FortiGate-VM Auto Scaling group to scale in (remove) 1 instance.

Minimum is 1. Maximum is 100.

The maximum time (in seconds) to wait for a master election to complete.

Minimum is 30. Maximum is 3600.

The minimum time (in seconds) permitted before a distributed license can be revoked from a non-responsive FortiGate and re-distributed.

Minimum is 300.

The length of time (in seconds) that Auto Scaling waits before checking an instance's health status.

Minimum is 60.

The Auto Scaling group waits for the cool down period (in seconds) to complete before resuming scaling activities.

Minimum is 60. Maximum is 3600.

Use this protocol to load balance traffic.

Balance web service traffic over this port if the internal web-service load balancer is enabled.

Minimum is 1. Maximum is 65535.

The number of consecutive health check failures required before considering a FortiGate instance unhealthy.

Minimum 3.

Add an optional predefined Elastic Load Balancer (ELB) to route traffic to web service in the private subnets. You can optionally use your own one or decide to not need one.

Optional. The destination path for health checks. This path must begin with a '/' character, and can be at most 1024 characters in length.

The length of time (in seconds) that a FortiGate-VM waits between sending heartbeat requests to the Autoscale handler.

Minimum is 30. Maximum is 90.

Number of consecutively lost heartbeats. When the Heartbeat loss count has been reached, the FortiGate-VM is deemed unhealthy and failover activities will commence.

Name of the S3 bucket (created in step 4 of Obtaining the deployment package) that contains the FortiGate Autoscale deployment package. Can only contain numbers, lowercase letters, uppercase letters, and hyphens (-). It cannot start or end with a hyphen (-).