How to install Ansible Automation Platform 2.6 (AAP) using the Containerized All-in-One Bundle in an offline environment. This installation focuses on the offline, containerized installation method, where all required components, including the Controller, Automation Hub, Automation Gateway, and Event-Driven are deployed via pre-packaged containers, without requiring direct internet access.
To ensure a consistent and secure setup of containerized Ansible Automation Platform, create a dedicated user on each host. Ansible Automation Platform connects as this user to run tasks on the host.
$ sudo adduser aap $ sudo passwd aap
$ sudo visudo -f /etc/sudoers.d/aap aap ALL=(ALL) NOPASSWD: ALL
The goal is for Ansible Automation Platform to log in as this user to run tasks on the host. This dedicated user can be used for each host by adding ansible_user=aap to the inventory file. Example: aap.example.org ansible_user=aap.
⚠️This user MUST ssh on the server.
Connect as aap user:
$ sudo -u aap -s
Then ssh on the server itself. The aap user must have an open ssh connection to be able to deploy the installation playbook.
$ ssh 4510bt-srv-0029 There were 0 failed login attempts since the last successful login.
Unpack
Put the zip file on your AAP server, in the /home/aap directory:
Inventory files define the information needed to customize the installation.
Go to the installation directory then open the inventory-growth file:
$ cd AAP $ vim inventory-growth
Then add the following configuration:
# Please consult the docs if you're unsure what to add # For all optional variables please consult the included README.md # or the Ansible Automation Platform documentation: # https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/containerized_installation
# This section is for your AAP Gateway host(s) # ----------------------------------------------------- [automationgateway] my-hostname.company.org
# This section is for your AAP Controller host(s) # ----------------------------------------------------- [automationcontroller] my-hostname.company.org
# This section is for your AAP Automation Hub host(s) # ----------------------------------------------------- [automationhub] my-hostname.company.org
# This section is for your AAP EDA Controller host(s) # ----------------------------------------------------- [automationeda] my-hostname.company.org
# This section is for the AAP database # ----------------------------------------------------- [database] my-hostname.company.org
# ----------------------------------------------------- # This section is for the AAP variables # ----------------------------------------------------- [all:vars]
Connect to the Web Interface with your admin credentials defined in the hub_admin_password variable.
Note about the certificates
By default, the installation program creates a self-signed Certificate Authority (CA) and uses it to generate self-signed TLS certificates for all Ansible Automation Platform services. The self-signed CA certificate and key are generated on one node under the ~/aap/tls/ directory and copied to the same location on all other nodes. This CA is valid for 10 years after the initial creation date.
Self-signed certificates are not part of any public chain of trust. The installation program creates a certificate truststore that includes the self-signed CA certificate under ~/aap/tls/extracted/ and bind-mounts that directory to each Ansible Automation Platform service container under /etc/pki/ca-trust/extracted/. This allows each Ansible Automation Platform component to validate the self-signed certificates of the other Ansible Automation Platform services. The CA certificate can also be added to the truststore of other systems or browsers as needed.
