Accessing a Cluster

The following section describes how to access the various services in the cluster.

To access the dashboard, you must log in to the cloud controller UI.

The Cloud Dashboard organizes clusters based on their status. Each cluster is represented by a tile.

Cluster Status

The possible cluster status is:

Cluster Details

You can access cluster details by clicking on the cluster's corresponding tile:

The cluster details page includes information about your cluster and all the nodes:


  • Access cluster actions by clicking on CLUSTER ACTIONS.
  • Access Ambari web UI, Ambari views, and other UIs by clicking on the icon. See Accessing the UIs.
  • Copy complete SSH information for a specific node by clicking on the icon.
  • If you enabled encryption for SSD storage attached to a specific node type, you will see the following icon .

The Cluster Details page includes the following section tabs:

Tab Description
HARDWARE Includes information about your cluster nodes: instance names, instance IDs (with links to the EC2 console), public IPs, and SSH connection information (with a copy option).
TAGS Lists user-defined tags, in the same order as you added them.
NETWORK Includes VPC and subnet IDs (with links to the VPC dashboard), remote access CIDR IP, and protected gateway access settings.
RECIPES Lists pre-install and post-install node recipes (with a copy option).
ADVANCED Lists Hive and Druid metastores, instance role setting for granting S3 access, and custom properties.
AUTO SCALING Allows you to view and manage (add, delete, configure) current auto scaling policies and settings.

Event History

The EVENT HISTORY tab shows you events logged for the cluster, with the most recent event at the top. For example, after your cluster has been created, the following messages will be written to the log:

2017-03-15 12:18:26
Ambari cluster built; Ambari ip:
2017-03-15 12:14:06
Building Ambari cluster; Ambari ip:
2017-03-15 12:09:15
Starting Ambari cluster services
2017-03-15 12:09:15
Setting up infrastructure metadata
2017-03-15 12:08:47
Bootstrapping infrastructure cluster
2017-03-15 12:08:47
Infrastructure successfully provisioned
2017-03-15 12:07:15
Infrastructure metadata collection finished
2017-03-15 12:07:14
Infrastructure creation took 173 seconds
2017-03-15 12:04:20
Creating infrastructure

Accessing a Cluster via SSH

If you plan to access the cluster via the command line clients, SSH into the master node instance in the cluster.

You can copy the full SSH statement from your Cluster Details page > HARDWARE section > SSH Connection column by clicking on the icon next to the master node:

Accessing Cluster Resources

For your convenience, you can access the Ambari web UI and other cluster components through a protected gateway:

The availability of UIs and their corresponding links depends on the Protected Gateway Access settings that you chose when creating your cluster:

Resource Description
Ambari Ambari Web UI and the Hive, Files and Tez views.
Zeppelin UI Zeppelin Web UI (if your cluster configuration included Zeppelin).
Cluster Components NameNode, ResourceManager, MapReduce JobHistoryServer and Spark History Server.

Accessing the UIs

Access to cluster resources and UIs is via the protected gateway. By default, the gateway has been configured with a self-signed certificate to be accessed via HTTPS. The first time you access the server, your browser will attempt to confirm that the SSL Certificate is valid. Since we are automatically generating a self-signed certificate, your browser will warn you about an Untrusted Connection and ask you to confirm a Security Exception. Depending on your browser, perform the steps below to proceed.

See Using Your Own SSL Certificate for more information on replacing the self-signed certificate with your own trusted certificate.

Browser Steps
Firefox Click Advanced > Click Add Exception... > Click Confirm Security Exception
Safari Click Continue
Chrome Click Advanced > Click Proceed...

If you are accessing cluster component UIs, you will be prompted to authenticate. Use the Cluster User credentials that you created when creating your cluster:


You can access the Ambari web UI once the create cluster process is complete. If you try to access Ambari while the cluster is being created, you will get a 502 Bad Gateway error.

Setting Configuration Properties

You can set configuration parameters by specifying custom properties when launching your cluster.

If you want to edit configuration configuration parameters when the cluster is already running, you can do this using Ambari web UI. Refer to Configuring Services documentation in the Ambari User Guide.

You can also set configuration parameters using Ambari API.