Stack Already Exists Error

Background

These scenarios that can be both counted as Stack Already Exists Error.

Scenario 1

After clicking on AWS CloudFormation Guide, you are re-directed to Stacks page instead of CloudFormation guide:

Notice the "FortiCNP" and "ContainerProtection" stacks already exist.

"FortiCNP" is the stack previously created for Cloud Protection.

"ContainerProtection" is the stack previously created for Container Protection.

The same thing can happen with "FortiCNPSecurityHubIntegration" stack in Cloud Protection.

Scenario 2

After completing all the steps in CloudFormation guide, "Stack already exists" error appeared preventing the setup to complete. This error indicated that the account was installed in Cloud Protection before, and there is already a stack created on the account.

Solution

This solution can be used for both scenario 1 and 2.

1. Log into your AWS account.
2. Click Services and search "CloudFormation".
3. Under Stacks, if you are adding AWS account on Cloud Protection, delete the stack named "FortiCNP" and "FortiCNPSecurityHubIntegration".

If you are adding AWS account on Container Protection, delete the stack named "ContainerProtection".



4. Go back to AWS CloudFormation, and repeat the steps with CloudFormation guide, the CloudFormation guide will complete with no error.