Troubleshooting

CREATE_FAILED error in CloudFormation stack

If you encounter a CREATE_FAILED error when you launch the Quick Start, relaunching the template with Rollback on failure set to Disabled is recommended. (This setting is under Advanced options in the AWS CloudFormation console, Configuring option settings page.) With this setting, the stack’s state is retained and the instance is left running, so you can troubleshoot the issue.

When you set Rollback on failure to Disabled, you continue to incur AWS charges for this stack. Ensure that you delete the stack when you finish troubleshooting.

See Troubleshooting AWS CloudFormation on the AWS website.

The deployment also fails if you select an instance type that is not supported in the region that was selected. Your desired instance type is available in your region if it is listed on the Instance types page for your region.

The election of the primary FortiGate-VM was not successful

If the election of the primary FortiGate-VM is not successful, reset the elected primary FortiGate-VM. If the reset does not solve the problem, contact support.

Resetting the elected primary FortiGate-VM

To reset the elected primary FortiGate-VM, navigate to the DynamoDB table <ResourceTagPrefix>-FortiGatePrimaryElection. Click the Items tab and delete the only item in the table.

A new primary FortiGate-VM is elected and a new record is created as a result.

For details on locating the DynamoDB table <ResourceTagPrefix>-FortiGatePrimaryElection, see Locating deployed resources.