1.4. Supported installation scenarios
Red Hat supports the following installations scenarios for Red Hat Ansible Automation Platform
This scenario includes installation of automation controller, including the web frontend, REST API backend, and database on a single machine. It installs PostgreSQL, and configures the automation controller to use that as its database. This is considered the standard automation controller installation scenario.
See "Installing automation controller with a database on the same node" in Installing Red Hat Ansible Automation Platform components on a single machine to get started.
This scenario includes installation of the automation controller server on a single machine and configures communication with a remote PostgreSQL instance as its database. This remote PostgreSQL can be a server you manage, or can be provided by a cloud service such as Amazon RDS.
See "Installing automation controller with an external managed database" in Installing Red Hat Ansible Automation Platform components on a single machine to get started.
This scenario includes installation of automation hub, including the web frontend, REST API backend, and database on a single machine. It installs PostgreSQL, and configures the automation hub to use that as its database.
See "Installing automation hub with a database on the same node" in Installing Red Hat Ansible Automation Platform components on a single machine to get started.
This scenario includes installation of the automation hub server on a single machine, and installs a remote PostgreSQL database, managed by the Red Hat Ansible Automation Platform installer.
See "Installing automation hub with an external database" in Installing Red Hat Ansible Automation Platform components on a single machine to get started.
This scenario includes installation of automation controller and automation hub with a database on the automation controller node, or a non-installer managed database.
See "Installing Red Hat Ansible Automation Platform with a database on the automation controller node or non-installer managed database" in Installing Red Hat Ansible Automation Platform to get started.
This scenario includes installation of automation controller and automation hub and configures communication with a remote PostgreSQL instance as its database. This remote PostgreSQL can be a server you manage, or can be provided by a cloud service such as Amazon RDS.
See "Installing Red Hat Ansible Automation Platform with an external managed database" in Installing Red Hat Ansible Automation Platform to get started.
This scenario includes installation of multiple automation controller nodes and an automation hub instance and configures communication with a remote PostgreSQL instance as its database. This remote PostgreSQL can be a server you manage, or can be provided by a cloud service such as Amazon RDS. In this scenario, all automation controller are active and can execute jobs, and any node can receive HTTP requests.
Running in a cluster setup requires any database that automation controller uses to be external—PostgreSQL must be installed on a machine that is not one of the primary or secondary tower nodes. When in a redundant setup, the remote PostgreSQL version requirements is PostgreSQL 12.
- See Clustering for more information on configuring a clustered setup.
-
Provide a reachable IP address for the
[automationhub]host to ensure users can sync content from Private Automation Hub from a different node.
See "Installing a multi-node Red Hat Ansible Automation Platform with an external managed database" in Multi-machine cluster intallation to get started.