Install Private Automation Hub

Task 3: Install Private Automation Hub

The next step on your way to a full AAP infrastructure is to install Private Automation Hub (PAH) as on-premise complement to Red Hat Automation Hub. PAH allows to mirror Automation Hub and Ansible Galaxy collections as well as own in-house content. And in addition PAH can act as a container registry for execution environments images.


  • Automation Controller is running & accessible
  • You can connect to your instance 2


  • Install Private Automation Hub on your instance number 2, the documentation is here in chapter 2.3.
  • The easiest way is to SSH into to the PAH instance, download the installer bundle like you did for Controller and install PAH locally (as in “don’t have the installer SSH to a remote machine”).

You can run the AAP installer in different ways, of course. You could run it from a competely different machine and connect to the hosts AAP is to be installed on, you could run it on the Controller instance like you did and have it connect to the PAH instance… but for now do it the easy way so you don’t have to fiddle with SSH keys and become settings. :)

  • So go ahead, SSH to instance 2, become root and download the installer bundle again
  • Take the inventory PAH example from the docs referenced above and adapt it to your needs.
    • Remember to replace localhost/ with the public FQDN
  • Run the installer with your customized inventory file


  • Opening and login to the Private Automation Hub web UI works.