Advanced proxy setup scenarios

In some cases, Cloudbreak using the proxy might vary depending on your Cloudbreak and cluster deployment.

This section describes two scenarios:

Scenario 1: Cloudbreak needs to go through a proxy to access the cloud provider APIs (and other public internet resources) but can talk to the cluster hosts directly.
Scenario 2: Cloudbreak needs to go through a proxy to access the cloud provider APIs (and other public internet resources) and the cluster hosts.

Scenario 1

In this scenario, Cloudbreak can resolve and communicate with the Ambari Server in the cluster hosts directly. For example, this can be a scenario where Cloudbreak is deployed in the same VPC/VNet as the clusters and will not go through the proxy. However, Cloudbreak will communicate to the public cloud provider APIs via the proxy.

To configure this scenario, set this setting in your Profile file:

HTTPS_PROXYFORCLUSTERCONNECTION = false

Scenario 2

In this scenario, Cloudbreak will connect to the Ambari Server through the configured proxy. For example, this can be a scenario where Cloudbreak is deployed to a different VPC/VNet than the cluster and must go through a proxy. Communication to the public cloud provider APIs also is via the proxy.

To configure this scenario, set this setting in your Profile file:

HTTPS_PROXYFORCLUSTERCONNECTION = true