Ansible Automation Hub: Publish & Manage Collections (Complete Guide)

Configure ansible.cfg

# ansible.cfg
[galaxy]
server_list = automation_hub, galaxy
[galaxy_server.automation_hub]
url = https://console.redhat.com/api/automation-hub/content/published/
auth_url = https://sso.redhat.com/auth/realms/redhat-external/protocol/openid-connect/token
token = <your-automation-hub-token>
[galaxy_server.galaxy]
url = https://galaxy.ansible.com/

Install Collections from Automation Hub

# Install a certified collection
ansible-galaxy collection install redhat.rhel_system_roles
# Install specific version
ansible-galaxy collection install cisco.ios:==8.0.0
# Install from requirements.yml
ansible-galaxy collection install -r requirements.yml

# requirements.yml
collections:
  - name: redhat.rhel_system_roles
    source: https://console.redhat.com/api/automation-hub/content/published/
  - name: ansible.netcommon
    version: ">=6.0.0"
  - name: cisco.ios

See also: AAP 2.6 Install Guide: Containerized, RPM & OpenShift Methods (2026)

Private Automation Hub

Private Automation Hub (PAH) is included with AAP. It lets you host collections internally.

Access PAH Web UI

https://your-pah-server/

Sync Collections from Red Hat

# In PAH UI:
# 1. Go to Collections → Repository Management
# 2. Add remote: console.redhat.com
# 3. Configure requirements (which collections to sync)
# 4. Click Sync

Publish Your Own Collections

# Build collection
ansible-galaxy collection build
# Publish to Private Automation Hub
ansible-galaxy collection publish \
  my_namespace-my_collection-1.0.0.tar.gz \
  --server https://your-pah-server/api/galaxy/content/inbound-collections/ \
  --token <your-pah-token>

Configure Clients for PAH

# ansible.cfg for teams using Private Automation Hub
[galaxy]
server_list = private_hub
[galaxy_server.private_hub]
url = https://your-pah-server/api/galaxy/content/published/
token = <your-pah-token>

Execution Environments with Automation Hub

# execution-environment.yml
dependencies:
  galaxy: requirements.yml
  python: requirements.txt
  system: bindep.txt
additional_build_steps:
  prepend_galaxy:
    - ENV ANSIBLE_GALAXY_SERVER_LIST=automation_hub
    - ENV ANSIBLE_GALAXY_SERVER_AUTOMATION_HUB_URL=https://your-pah-server/api/galaxy/content/published/
    - ENV ANSIBLE_GALAXY_SERVER_AUTOMATION_HUB_TOKEN=$PAH_TOKEN

See also: AAP 2.6 Tested Deployment Models: Growth & Enterprise Topologies Guide

Certified vs Validated Collections

Certified Collections

Validated Collections

Collection Namespaces

# List installed collections
ansible-galaxy collection list
# Search Automation Hub (via API)
curl -H "Authorization: Bearer $TOKEN" \
  "https://console.redhat.com/api/automation-hub/v3/plugin/ansible/search/collection-versions/?name=rhel_system_roles"

Best Practices

FAQ

What is Ansible Automation Hub?

Ansible Automation Hub is Red Hat's hosted repository for certified and validated Ansible collections. It provides enterprise-grade, tested content with Red Hat support. Access requires a Red Hat Ansible Automation Platform subscription.

What is the difference between Ansible Galaxy and Automation Hub?

Galaxy is public and community-driven — anyone can publish. Automation Hub hosts Red Hat certified and validated collections with commercial support. For production enterprise use, Automation Hub provides tested, supported content.

What is Private Automation Hub?

Private Automation Hub (PAH) is a self-hosted collection repository included with AAP. It lets organizations host internal collections and sync certified content from Red Hat for air-gapped or regulated environments.

How do I install collections from Automation Hub?

Configure your API token in ansible.cfg under [galaxy_server.automation_hub], then use ansible-galaxy collection install collection_name. The token authenticates your Red Hat subscription.

Can I publish my own collections to Automation Hub?

You can publish to Private Automation Hub (self-hosted). Publishing to the public Red Hat Automation Hub requires a Red Hat partner agreement. For community sharing, use Ansible Galaxy.

Conclusion

Automation Hub provides the enterprise backbone for Ansible content management. Use it for certified collections in production, Private Automation Hub for internal distribution, and Galaxy for community content in development.

Related Articles