Using Anaconda Distribution with AE4#

Configuring firewall settings#

If platform users will use Navigator online, you may need to whitelist the necessary sites in your network’s firewall settings so that Navigator can reach these sites:

If platform users will use Navigator offline, conda environment creation will be limited to the packages available in their package cache. Using Navigator in offline mode is equivalent to using the create, install, remove, and update conda commands with the --offline flag so that conda does not connect to the internet. If your users will use Navigator offline, you may want to change the Navigator icons that link to the web.

NOTE: If Navigator detects that internet access is not available, it automatically enables offline mode. Users can also select Anaconda Navigator > Preferences and check the Enable offline mode option to work in offline mode any time, even when internet access is available.

Configuring conda#

If platform users will use conda to install packages, they can configure conda to search a specific set of channels for packages.

As an Administrator, you can also configure conda at the system level, which will override any user-level configuration.

Configuring Navigator#

By default, Navigator includes icons linking to the GitHub, YouTube, and Twitter pages of Anaconda Inc. Users can change or remove these links by editing the configuration file located here: HOME_DIR/.anaconda/navigator/anaconda-navigator-config.yml.

The configuration file uses key-value pairs in the form key: value, such as github_url: Each of the three values github_url youtube_url and twitter_url may be set to any URL or null. If the value is null, Navigator does not display that icon.

As an Administrator, you can create a configuration file for Navigator to enable users to access the Anaconda Enterprise 4 Repository and set additional parameters that are not exposed in the preferences dialog. This main configuration file stores all user preferences for Navigator, and is located here: ~/.anaconda/navigator/anaconda-navigator.ini.

The configuration file includes main and home sections, each containing sets of key-value pairs in .ini format.

You can use it to customize the following options in the main section:

  • default_anaconda_api_url: This points to the internal Anaconda Enterprise 4 Repository API endpoint.

NOTE: This URL must end with /api— it is not simply the homepage of your instance. This API reads the configuration data from your instance to set UI behavior and text, such as the Sign in to… link in the the top right corner of the Navigator window.

  • default_ssl_certificate — This can be set to True, False, or a path to an existing and valid SSL certificate file.

NOTE: If your Anaconda Enterprise 4 Repository instance requires an SSL cert/RSA key to access it, that information must exist in a text file on the user’s machine, and pointed to via the path specified here in the .ini file. The format for the text file should resemble the following:


<actual cert here>



<actual key here>


  • twitter_url — This can be configured to point to your company’s account, or be set to None to display no icon.

  • youtube_url — This can be configured to point to your company’s account, or be set to None to display no icon.

  • github_url — This can be configured to point to your company’s account, or be set to None to display no icon.

And set this option in the home section:

  • vscode_enable — This can be set to True or False, based on whether you want to enable or disable VSCode from appearing on the Home tab and making queries to the Microsoft endpoint from within the application.

For example:

default_anaconda_api_url =
default_ssl_certificate = /path/to/certificate/file.pem

# Custom URLS
twitter_url =
youtube_url =
github_url =

vscode_enable = False

After making your changes, save and close the .ini file, then launch Navigator to update the .condarc and anaconda-client configurations to reflect the customized settings you’ve specified within it.