Community Articles
Find and share helpful community-sourced technical articles
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.
Labels (1)
Community Manager

Symptoms

When creating an AWS Environment through Quickstart, the environment attempts to create, but shows Failed.

Applies To

Cloudera Altus Environments setup with Quickstart

Cause

There can be several causes:

  • Your limit of VPCs have been reached.
  • Your Cloudwatch log group may already exist.
  • Some other limit in AWS has been reached.
  • You may not have proper permissions in AWS.

Troubleshooting Steps

Beneath the AWS Console -> CloudFormation, select the Stack that just failed to deploy.

Expand Events and work from the bottom up to see what the event that failed first.

If a limit was exceeded, open an issue with AWS support or request a limit increase beneath EC2 -> limits.

If a authorization role is needed for your account, contact your AWS account owner to provide you with that role.

Otherwise, correct any failure other failure cause you see (e.g. duplicate CloudWatch log group, etc), delete the stack, and attempt to Quickstart the environment again.

 

402 Views
Don't have an account?
Coming from Hortonworks? Activate your account here
Version history
Revision #:
4 of 4
Last update:
‎06-26-2018 08:55 AM
Updated by:
 
Top Kudoed Authors