The following describes the general methods for troubleshooting a CloudFormation issue encountered while deploying eMAM using CFT on AWS. You can use the AWS CloudFormation console to monitor the status of eMAM CloudFormation stack.

1. CloudFormation console Events tab: While deploying eMAM using CFT, in AWS CloudFormation console, click on the Events tab to find information on stack creation, updates, and deletions. If the stack fails to create, information on the Events tab usually gives you a general idea what has gone wrong. From this list, find the failure event and then view the status reason for that event. The status reason might contain an error message from AWS CloudFormation or from a particular service that can help you troubleshoot your problem.
   

2. CloudWatch log group: The eMAM system CloudFormation template creates a CloudWatch log group into which the log files are copied from the EC2 instance. The CloudWatch log group contains log streams, which include the ID of the instance with the log file name. This allows you to identify to which EC2 instance the log file pertains. If CloudFormation stack creation succeeds, the stack output parameters provide a link to the log group in the AWS Management Console.
   If stack creation fails, go to the CloudFormation Resources list in the AWS Management Console to find the log group. Note that if stack creation fails before any instances are launched, a log group might not be created.
   

Troubleshooting at CFT Stack level

Use the CloudFormation console to view the status of your stack. In the console, you can view a list of stack events while your stack is being created, updated, or deleted. From this list, find the failure event and then view the status reason for that event. The status reason might contain an error message from AWS CloudFormation or from a particular service that can help you troubleshoot your problem.

1. Delete stack fails: To resolve this situation, try the following:

• Some resources must be empty before they can be deleted. For example, you must delete all objects in an Amazon S3 bucket or remove all instances in an Amazon EC2 security group before you can delete the bucket or security group.

• Ensure that you have the necessary IAM permissions to delete the resources in the stack. In addition to AWS CloudFormation permissions, you must be allowed to use the underlying services, such as Amazon S3 or Amazon EC2.

2. Insufficient IAM permissions: When you work with an AWS CloudFormation stack, you not only need permissions to use AWS CloudFormation, you must also have permission to use the underlying services that are described in your template. For example, if you're creating an Amazon S3 bucket or starting an Amazon EC2 instance, you need permissions to Amazon S3 or Amazon EC2.

• Review your IAM policy and verify that you have the necessary permissions before you work with AWS CloudFormation stacks.

3. Invalid value or unsupported resource property : When you create or update an AWS CloudFormation stack, your stack can fail due to invalid input parameters, unsupported resource property names, or unsupported resource property values.For input parameters, verify that the resource exists.
   For example, when you specify an Amazon EC2 key pair or VPC ID, the resource must exist in your account and in the region in which you are creating or updating your stack.

• You can use AWS-specific parameter types to ensure that you use valid values. For resource property names and values, update your template to use valid names and values. For a list of all the resources and their property names, see AWS resource and property types reference

• Also, Amazon Rekognition is not available in all AWS Regions. For a list of all regions where Amazon Rekognition is available, see the AWS Region table.

4. Limit exceeded: Verify that you didn't reach a resource limit. For example, the default maximum number of Amazon EC2 instances that you can launch is 20. If try to create more Amazon EC2 instances than your account limit, the instance creation fails and you receive the error Status=start_failed.

• To view the default AWS limits by service, see AWS service limits in the AWS General Reference.
• You can delete excess resources or request a limit increase.

5. Security group does not exist in VPC: Verify that the security group exists in the VPC that you specified.

• If the security group exists, ensure that you specify the security group ID and not the security group name.

6. Resource failed to stabilize during a create, update, or delete stack operation: A resource didn't respond because the operation exceeded the AWS CloudFormation timeout period or an AWS service was interrupted.

• For service interruptions, check that the relevant AWS service is running, and then retry the stack operation.

Troubleshooting at eMAM UI level

1. Login failed: Ensure the login credentials used are correct and taken from the Outputs tab of the CloudFormation Stack console.

   Default Username: admin@emamcloud.com
   Default Password: Check the Outputs tab

2. Login screen does not appear: This could happen when the server is still in initializing stage, so please wait for 5 minutes and then try again.