Articles in this section

How to Block Access to Anaconda Public Repositories

Some organizations want their users to install packages only from approved and governed sources. Blocking access to Anaconda public repositories helps ensure users in your organization can only retrieve packages from the sources you allow.

Before applying firewall, proxy, or DNS rules, decide which outcome you want:

  • Block public packages only
    Users can still download installers, but they cannot install packages from Anaconda public repositories.
  • Block public packages and installers
    Users cannot download installers or install packages from Anaconda public repositories.
  • Allow governed access only
    Users retrieve packages only from your authenticated Anaconda-managed repository.

Block public packages only

Choose this option if you want users to keep access to Anaconda or Miniconda installers, but prevent package installation from Anaconda public repositories.

Block these URLs:

  • https://repo.anaconda.com/pkgs/
  • https://conda.anaconda.org/main
  • https://conda.anaconda.org/msys2
  • https://conda.anaconda.org/free
  • https://conda.anaconda.org/r
  • https://conda.anaconda.org/anaconda
  • https://conda-static.anaconda.org/main
  • https://conda-static.anaconda.org/msys2
  • https://conda-static.anaconda.org/r
  • https://conda-static.anaconda.org/anaconda

Leave these URLs open:

  • https://repo.anaconda.com/archive
  • https://repo.anaconda.com/miniconda
  • https://pro.anaconda.cloud/archive
  • https://pro.anaconda.cloud/miniconda

Important: Do not block the entire conda.anaconda.org or conda-static.anaconda.org domain unless you also want to block community channels such as conda-forge, bioconda, and pytorch.

Block public packages and installers

Choose this option if you want users to be unable to access both Anaconda public packages and Anaconda-hosted installers.

Block these URLs:

  • https://repo.anaconda.com/
  • https://conda.anaconda.org/main
  • https://conda.anaconda.org/msys2
  • https://conda.anaconda.org/free
  • https://conda.anaconda.org/r
  • https://conda.anaconda.org/anaconda
  • https://conda-static.anaconda.org/main
  • https://conda-static.anaconda.org/msys2
  • https://conda-static.anaconda.org/r
  • https://conda-static.anaconda.org/anaconda

You may also choose to block this legacy URL:

  • https://repo.continuum.io/pkgs/

Important: Blocking https://repo.anaconda.com/ blocks both package and installer access under that domain.

Important: Do not block the entire conda.anaconda.org or conda-static.anaconda.org domain unless you also want to block community channels such as conda-forge, bioconda, and pytorch.

Allow governed access only

Choose this option if you want users to install packages only from Anaconda’s authenticated managed repository.

Keep these URLs available:

  • https://repo.anaconda.cloud/repo/
  • https://repo-prod-us-east-1.anaconda.cloud/repo/

If your goal is to prevent access to Anaconda public repositories while preserving governed access, block these public URLs:

  • https://repo.anaconda.com/pkgs/
  • https://conda.anaconda.org/main
  • https://conda.anaconda.org/msys2
  • https://conda.anaconda.org/free
  • https://conda.anaconda.org/r
  • https://conda.anaconda.org/anaconda
  • https://conda-static.anaconda.org/main
  • https://conda-static.anaconda.org/msys2
  • https://conda-static.anaconda.org/r
  • https://conda-static.anaconda.org/anaconda

If you also want to prevent installer downloads from Anaconda public sources, block:

  • https://repo.anaconda.com/

If users should still be able to download installers, leave these URLs open:

  • https://repo.anaconda.com/archive
  • https://repo.anaconda.com/miniconda
  • https://pro.anaconda.cloud/archive
  • https://pro.anaconda.cloud/miniconda

Additional notes

  • https://anaconda.org is a web interface for browsing packages and channels. Conda package managers do not use this domain for package downloads.
  • Blocking anaconda.org alone does not prevent access to Anaconda public repositories.
  • The exact configuration steps depend on your organization’s firewall, proxy, or DNS tools.
  • After applying changes, test from an end-user environment to confirm only approved sources remain accessible.
Was this article helpful?
1 out of 1 found this helpful