Troubleshoot the AWS CloudFormation Template deployment

Use this information to troubleshoot issues relating to CloudFormation Template deployment.

[ERROR]: Error parsing parameter '--tempate-body': Unable to load param file

The CloudFormation template fails to deploy when running the AWS CLI CloudFormation command.

Cause

There is an error in the S3 bucket template and the parameters file cannot be loaded.

Solution

1. Navigate to the Setup Data Ingestion page and click the Download template button to download a new copy of the S3 bucket template.
2. Verify that you are running the AWS CLI CloudFormation command from the directory where the S3 bucket template file is located.
3. If you are still seeing this error message, Contact Splunk Support.

[ERROR]: Error parsing parameter '--tempate-body': JSON does not exist

The CloudFormation template fails to deploy when running the AWS CLI CloudFormation command.

Cause

The CloudFormation template cannot be found.

Solution

1. Navigate to the Setup Data Ingestion page and click the Download template button to download a new copy of the CloudFormation template.
2. Verify that you are running the AWS CLI CloudFormation command from the directory where the CloudFormation template file is located.
3. If you are still seeing this error message, Contact Splunk Support.

Mismatch error: Stacks in regions not fully deleted

Cause

If you remove a region from an existing AWS input, but fail to run the accompanying CLI command, you will cause a region mismatch. If you delete this input while it has a mismatch status, the delete input process will fail to delete the stack on the region that you removed.

Solution

To prevent this issue, don't mark a mismatched data input for deletion. Resolve the mismatch status before you mark the input for deletion.

If there is a mismatch input already being marked for deletion, you must identify exactly what the mismatch is, and remove the mismatched resources on your AWS deployment manually.