Chapter 5. Network ports and protocols Red Hat Ansible Automation Platform uses several ports to communicate with its services. These ports must be open and available for incoming connections to the Red Hat Ansible Automation Platform server in order for it to work. Ensure that these ports are available and are not being blocked by the server firewall. The following architectural diagram is an example of a fully deployed Ansible Automation Platform with all possible components. The following tables show the default Red Hat Ansible Automation Platform destination ports required for each application. Note The following default destination ports and installer inventory listed are configurable. If you choose to configure them to suit your environment, you might experience a change in behavior. Table 5.1. PostgreSQL Port Protocol Service Direction Installer Inventory Variable Required for 22 TCP SSH Inbound and Outbound ansible_port Remote access during installation 5432 TCP Postgres Inbound and Outbound pg_port Default port ALLOW connections from controller(s) to database port Table 5.2. Automation controller Port Protocol Service Direction Installer Inventory Variable Required for 22 TCP SSH Inbound and Outbound ansible_port Installation 80 TCP HTTP Inbound nginx_http_port UI/API 443 TCP HTTPS Inbound nginx_https_port UI/API 5432 TCP PostgreSQL Inbound and Outbound pg_port Open only if the internal database is used along with another component. Otherwise, this port should not be open Hybrid mode in a cluster 27199 TCP Receptor Inbound and Outbound receptor_listener_port ALLOW receptor listener port across all controllers for mandatory and automatic control plane clustering Table 5.3. Hop Nodes Port Protocol Service Direction Installer Inventory Variable Required for 22 TCP SSH Inbound and Outbound ansible_port Installation 27199 TCP Receptor Inbound and Outbound receptor_listener_port Mesh ALLOW connection from controller(s) to Receptor port Table 5.4. Execution Nodes Port Protocol Service Direction Installer Inventory Variable Required for 22 TCP SSH Inbound and Outbound ansible_port Installation 80/443 TCP SSH Inbound and Outbound Fixed value (maps to Table 5.7 Automation hub's "User interface" port) Allows execution nodes to pull the execution environment image from automation hub 27199 TCP Receptor Inbound and Outbound receptor_listener_port Mesh - Nodes directly peered to controllers. No hop nodes involved. 27199 is bi-directional for the execution nodes ALLOW connections from controller(s) to Receptor port (non-hop connected nodes) ALLOW connections from hop node(s) to Receptor port (if relayed through hop nodes) Table 5.5. Control Nodes Port Protocol Service Direction Installer Inventory Variable Required for 22 TCP SSH Inbound and Outbound ansible_port Installation 27199 TCP Receptor Inbound and Outbound receptor_listener_port Mesh - Nodes directly peered to controllers. Direct nodes involved. 27199 is bi-directional for execution nodes ENABLE connections from controller(s) to Receptor port for non-hop connected nodes ENABLE connections from hop node(s) to Receptor port if relayed through hop nodes 443 TCP Podman Inbound nginx_https_port UI/API Table 5.6. Hybrid Nodes Port Protocol Service Direction Installer Inventory Variable Required for 22 TCP SSH Inbound and Outbound ansible_port Installation 27199 TCP Receptor Inbound and Outbound receptor_listener_port Mesh - Nodes directly peered to controllers. No hop nodes involved. 27199 is bi-directional for the execution nodes ENABLE connections from controller(s) to Receptor port for non-hop connected nodes ENABLE connections from hop node(s) to Receptor port if relayed through hop nodes 443 TCP Podman Inbound nginx_https_port UI/API Table 5.7. Automation hub Port Protocol Service Direction Installer Inventory Variable Required for 22 TCP SSH Inbound and Outbound ansible_port Installation 80 TCP HTTP Inbound Fixed value User interface 443 TCP HTTPS Inbound Fixed value User interface 5432 TCP PostgreSQL Inbound and Outbound automationhub_pg_port Open only if the internal database is used along with another component. Otherwise, this port should not be open Table 5.8. Services Catalog Port Protocol Service Direction Installer Inventory Variable Required for 22 TCP SSH Inbound and Outbound ansible_port Installation 443 TCP HTTPS Inbound nginx_https_port Access to Service Catalog user interface 5432 TCP PostgreSQL Inbound and Outbound pg_port Open only if the internal database is used. Otherwise, this port should not be open Table 5.9. Red Hat Insights for Red Hat Ansible Automation Platform URL Required for http://api.access.redhat.com:443 General account services, subscriptions https://cert-api.access.redhat.com:443 Insights data upload https://cert.cloud.redhat.com:443 Inventory upload and Cloud Connector connection https://cloud.redhat.com Access to Insights dashboard Table 5.10. Automation Hub URL Required for https://console.redhat.com:443 General account services, subscriptions https://catalog.redhat.com Indexing execution environments https://sso.redhat.com:443 TCP https://automation-hub-prd.s3.amazonaws.com https://automation-hub-prd.s3.us-east-2.amazonaws.com/ Firewall access https://galaxy.ansible.com Ansible Community curated Ansible content https://ansible-galaxy-ng.s3.dualstack.us-east-1.amazonaws.com https://registry.redhat.io:443 Access to container images provided by Red Hat and partners https://cert.cloud.redhat.com:443 Red Hat and partner curated Ansible Collections Table 5.11. Execution Environments (EE) URL Required for https://registry.redhat.io:443 Access to container images provided by Red Hat and partners cdn.quay.io:443 Access to container images provided by Red Hat and partners cdn01.quay.io:443 Access to container images provided by Red Hat and partners cdn02.quay.io:443 Access to container images provided by Red Hat and partners cdn03.quay.io:443 Access to container images provided by Red Hat and partners Important Image manifests and filesystem blobs are served directly from registry.redhat.io . However, from 1 May 2023, filesystem blobs are served from quay.io instead. To avoid problems pulling container images, you must enable outbound connections to the listed quay.io hostnames. Make this change to any firewall configuration that specifically enables outbound connections to registry.redhat.io . Use the hostnames instead of IP addresses when configuring firewall rules. After making this change, you can continue to pull images from registry.redhat.io . You do not require a quay.io login, or need to interact with the quay.io registry directly in any way to continue pulling Red Hat container images. For more information, see the article here

Commands: