Restricted network installation¶

You can install DataRobot in a restricted network by implementing the prerequisites outlined below. This type of installation is also referred to as an offline or restricted network installation.

This section addresses application-specific requirements for installations with the latest version of DataRobot. Obtaining images and installation artifacts is not in scope of these instructions.

Access to the image registry¶

Your cluster must have network access to the image registry. If you need to access external registries, like Docker Hub or Amazon Elastic Container Registry (ECR), you must also grant access to the Content Delivery Networks (CDNs) that they use.

• If you require access to Docker Hub, ensure you have connectivity to the following resources (replace <region-name> with the appropriate AWS region):

  • auth.docker.io
  • registry-1.docker.io
  • production.cloudflare.docker.com
  • docker-images-prod.s3.dualstack.<region-name>.amazonaws.com (for AWS VPC only)

• If you require access to AWS ECR, ensure you have connectivity to the following resource (replace <region-name> with the appropriate AWS region):

  • prod-<region-name>-starport-layer-bucket.s3.<region-name>.amazonaws.com

Additional components¶

• Tile Server in restricted network.
• Generative AI service in offline clusters.

DataRobot FQDN access¶

The cluster must be able to resolve and access the Fully Qualified Domain Name (FQDN) of your DataRobot installation.