> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.itential.com/itential-gateway/4/system-requirements/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server. # Gateway system requirements > Review the server specifications, software requirements, and registry credentials you need before installing Itential Gateway. Itential Gateway requires specific hardware, software, and network configurations before you can install and run it. Review the requirements on this page to prepare your environment. > **Note** > > For the most current version-specific requirements, including third-party software compatibility, refer to the [Gateway release notes](/itential-gateway/4/release-notes/overview) for your release. You can also refer to the [Gateway Dependencies](#gateway-dependencies) table for a consolidated list of supported dependencies. ## Server specifications The following table lists the required server specifications for production and development environments. | Specification | Requirement | Production | Development | | ------------------ | --------------------------------- | ---------------------- | ----------------------------------- | | CPU | 64-bit x86 | 16 cores | 4 cores | | OS | RHEL / Rocky / Amazon Linux | 8 or 9 / 8 or 9 / 2023 | 8 or 9 / 8 or 9 / 2023 | | RAM | DDR5 DRAM 3200 MHz | 32 GB | 16 GB | | Disk (SSD or NVMe) | Total / `/opt/automation-gateway` | 50 GB / 50 GB | Minimum: 10 GB / Recommended: 20 GB | > **Note** > > If you use a large number of custom scripts, content, or logging, you may need to increase CPU, RAM, and disk space allocations beyond these recommendations. ## Software requirements Gateway is a pip-installed Python package supported on RHEL, Rocky, and Amazon Linux. You can use any method to install Python or Ansible as long as the versions match the requirements for your Gateway release. The following software is generally required: * RHEL 8 or 9 / Rocky 8 or 9 / Amazon Linux 2023 * Python 3.9 * Ansible-Core (refer to your release notes for supported versions) You must also install any integrations you plan to use, such as Ansible, Terraform, or Nornir. ## Implementation considerations Gateway resides on the same server as your Ansible implementation. If you have multiple Ansible implementations, you must install Gateway on each server. Optionally, you can use Itential adapters to connect each Gateway installation to the Itential Automation Platform (IAP) and manage all of your Ansible networks from a single point. ## Software repository and registry credentials > **Warning** > > You need access to the Itential pip registry to download and install Gateway. To get your credentials, contact the [Itential Service Desk](https://itential.atlassian.net/servicedesk/customer/portals). For all Gateway installation methods, your customer account is assigned to one of two software repositories: **Nexus** or **JFrog**. You'll receive your repository assignment in a welcome email after Itential grants you access. To ensure the install reflects the correct `REGISTRY_URL` for your assigned repository, use the appropriate value from the sections that follow. ### Install script > **Note** > > The following script contains a generic placeholder for the `REGISTRY_URL` variable. Replace it with the value for your assigned repository. ```bash echo "## CUSTOMIZE THESE VARIABLES BEFORE RUNNING THIS SCRIPT: ##" && \ export AUTOMATION_GATEWAY_VERSION="" && \ export REGISTRY_USERNAME="" && \ export REGISTRY_PASSWORD="" && \ export REGISTRY_URL=<> echo "## UPGRADE THE AUTOMATION GATEWAY PIP PACKAGE: ##" && \ sudo pip3 install --upgrade -v automation-gateway==$AUTOMATION_GATEWAY_VERSION --extra-index-url https://$REGISTRY_USERNAME:$REGISTRY_PASSWORD@$REGISTRY_URL ``` ### Customer accounts assigned to JFrog Set the `REGISTRY_URL` variable to the following value if your account is assigned to the **JFrog** repository: ```text "itential.jfrog.io/artifactory/automation-gateway/" ``` ### Customer accounts assigned to Nexus Set the `REGISTRY_URL` variable to the following value if your account is assigned to the **Nexus** repository: ```text "registry.aws.itential.com/repository/automation-gateway-release/simple" ``` ## Gateway dependencies | Gateway Version | python | openssl | haproxy | pip | terraform | nornir | netmiko | | :-------------- | :---------: | :---------: | :---------: | :----: | :-----------: | :---------: | :---------: | | 4.4 | 3.12.x | 1.1.0-1.2.0 | 2.0.0-3.0.0 | 26.2.1 | 1.2.9 | 3.3.0-4.0.0 | 4.5.0 | | 4.3 | 3.9.x | 1.1.0-1.2.0 | 2.0.0-3.0.0 | 20.2.4 | 1.2.9 | 3.0.0-4.0.0 | 4.1.2 | | 2023.3 | 3.9.x | 1.1.0-1.2.0 | 2.0.0-3.0.0 | 20.2.4 | 1.2.9 | 3.0.0-4.0.0 | 4.1.2 | | 2023.2 | 3.9.x | 1.1.0-1.2.0 | 2.0.0-3.0.0 | 20.2.4 | 1.2.9 | 3.0.0-4.0.0 | 4.1.2 | | 2023.1 | 3.9.x | 1.1.0-1.2.0 | 2.0.0-3.0.0 | 20.2.4 | 1.2.9 | 3.0.0-4.0.0 | 4.1.2 | | 2022.1 | 3.9.5-4.0.0 | 1.1.0-1.2.0 | 2.0.0-3.0.0 | 20.2.4 | 0.12.0-0.13.0 | 3.0.0-4.0.0 | 3.0.0-4.0.0 | Notes: * The following grpc pinned libraries are used to test Gateway: pygnmi==0.8.9, grpcio==1.53.0. * The gcc-c++ and make packages should be installed from your OS distribution. * The gcc is only required for installation and can be safely removed after a successful install. The gcc is not needed for operation. * The following development packages are required to install Gateway: libffi-dev, openssl-dev, python-dev, sqlite-dev. * One or more of the following packages may be required by the specific Ansible modules you're using: psutil, pycrypto, paramiko, ncclient, lxml, nitrosdk-python, jxmlease. * Check the [Ansible documentation](https://docs.ansible.com/) for the roles you're planning to use for additional package requirements. > Review the server specifications, software requirements, and registry credentials you need before installing Itential Gateway.