> ## Documentation Index
> Fetch the complete documentation index at: https://anaconda.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Pre-install checklist

It’s essential that the systems in your environment where you will install Anaconda Enterprise
meet [ALL of the requirements outlined here](./reqs). The installer performs some pre-flight checks,
and only allows installation to continue on nodes that are configured correctly, but doesn’t verify *all requirements* are met.

We’ve created this pre-install checklist to help you **verify that you’ve accounted for everything before you begin**, and ensure your installation is successful. Consider printing out a copy and physically checking off items as you go.

<Note>
  We’ve also packaged a pre-flight script that you can use to verify whether the systems on which you plan to install Anaconda Enterprise meet the minimum requirements to install successfully. [Follow these instructions](./pre-flight) to install and run the script.
</Note>

\[ ] I’ve verified that all nodes in the cluster meet [the minimum or recommended specifications](./reqs#hardware-requirements) for CPU, RAM and disk space.

\[ ] I’ve verified that all nodes in the cluster meet [the minimum IOPS required](./reqs#disk-iops-requirements) for reliable performance.

\[ ] I’ve verified that there is [50GB of free space available](./reqs#storage-and-memory-requirements) in the `/tmp` directory (or another temporary directory to be used during installation) on each node in the cluster.

\[ ] I’ve verified that **all cluster nodes are operating the same version of the OS**, and that [the OS version is supported](./reqs#operating-system-requirements) by Anaconda Enterprise.

\[ ] I’ve used the Network Time Protocol (NTP) to synchronize computer system clocks, and I’ve verified that **the clock of each node in the cluster is in sync with the others**. (Instructions for using NTP are provided [here](https://www.tecmint.com/synchronize-time-with-ntp-in-linux/).)

\[ ] I’ve verified that I have `sudo` access on all systems, and [the firewall is configured correctly](./reqs#security-requirements).

\[ ] I’ve verified that [all required kernel modules](./reqs#kernel-module-requirements) are loaded.

\[ ] I’ve verified that [the system control settings](./reqs#system-control-settings) are set correctly.

\[ ] I’ve verified that any GPUs to be used with Anaconda Enterprise have [a supported NVIDIA CUDA driver installed](./reqs#gpu-requirements).

\[ ] I’ve verified that the system meets [all network port requirements](./reqs#network-requirements), whether the specified ports need to be open internally, externally, or during installation only.

\[ ] I’ve verified that any firewalls used for network security have been *temporarily* disabled, for the window of time when Anaconda Enterprise is being installed.

\[ ] I’ve verified that the domains required for *online* package mirroring have been whitelisted, if applicable.

\[ ] *If I intend to replace the self-signed certificates generated during installation with others*, I’ve gathered [all the information and files for the TLS/SSL certificates I will use](./certs).

\[ ] I’ve verified that the Anaconda Enterprise domain get resolved to the IP address of the master node, whether through an alias (A) record or canonical name (CNAME).

\[ ] I’ve verified that any wildcard DNS entries for my organization’s domain names meet [the DNS requirements outlined here](./reqs#dns-requirements).

\[ ] I’ve verified that the `/etc/resolv.conf` file on all the nodes **DOES NOT** include the `rotate` option.

\[ ] I’ve verified that any existing installations of Docker (and `dockerd`), `dnsmasq`, and `lxd` have been removed from all nodes, as they will conflict with Anaconda Enterprise.

\[ ] I’ve verified that all web browsers to be used to access Anaconda Enterprise are [supported by the platform](./reqs#browser-requirements).