Outbound network access destinations

Review this section to find out which specific outbound destinations must be available in order to install and configure Cloudbreak in an environment with limited outbound network access.

To install and configure Cloudbreak, specific outbound destinations must be available. The following outbound destinations must be available:


Destination	Description
*.docker.io	Obtain the Docker images for Cloudbreak.
raw.githubusercontent.com github.com s3.amazonaws.com *.cloudfront.net	Obtain Cloudbreak dependencies.
cloudbreak-imagecatalog.s3.amazonaws.com	The default Cloudbreak image catalog used for VMs. Refer to Custom images documentation for more information on image catalogs.

Once Cloudbreak is installed and configured, you will need the following outbound destinations available in order to communicate with the cloud provider APIs to obtain cloud resources for clusters.


Cloud provider	Cloud provider API destinations
Amazon Web Services	*.amazonaws.com
Microsoft Azure	.microsoftonline.com .windows.net *.azure.com
Google Cloud Platform	accounts.google.com *.googleapis.com

To install the cluster software, you can:

a) use the public hosted repositories provided by Hortonworks, or

b) specify your own local hosted repositories when you create a cluster.

If you choose to (a) use the public hosted repositories, be sure to allow outbound access to the following destinations:

private-repo-1.hortonworks.com
public-repo-1.hortonworks.com