Question Is the Cloudera Altus CLI supported for Windows systems? Answer Starting with the Cloudera Altus CLI Version 1.1.3, installation is available through pip, as long as the following minimum requirements are met:   Minimum version of Python 3.6+   1) Download and Install Python for Windows according to the website's instructions:      https://www.python.org/downloads/windows/   2) Open a Command Prompt (Windows Key + R), then type cmd and hit enter.   3) In the Command prompt window, run the command to update the Windows environment to add the newly installed Python folder to the system path:   setx "%PATH%";C:\<Python_Install_destination>\Scripts;      For example, if Python 2.7 was installed in it's default location, the following command would be run:     setx "%PATH%";C:\Python36\Scripts;   4) In the same Window, run the pip installer to install the Cloudera Altus CLI Utility:     pip install altuscli   5) Once the Cloudera Altus CLI is installed, confirm its functionality by running altus --version as shown below:        ... View more

Question Can I use a bootstrap script to further configure the cluster?  Answer Instance bootstrap scripts are executed on all the cluster instances immediately after startup before any services are configured and started.  You can use it to install additional OS packages or add application dependencies (e.g. copy a jar to the cluster, etc). This is not intended to be a mechanism for cluster configuration. ... View more

Question I noticed the Cloudera Altus documentation is not avaialable at the standard location for Cloudera documentation at:   https://www.cloudera.com/documentation.html   Where is this documentation available? Answer When you login with your Cloudera credentials to:   https://console.altus.cloudera.com/   There is a pulldown available in the upper right corner for Support -> Documentation that links to the docummentation at:   https://console.altus.cloudera.com/support/documentation.html   Documentation will also be available with the standard Cloudera documentation in an upcoming release. ... View more

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.   References https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html ... View more