AWX — Web UI, API, and Task Engine for Ansible

What it is

AWX is the upstream open-source project behind Red Hat Ansible Automation Platform. It provides a web-based user interface, REST API, and task engine built on top of Ansible. AWX lets teams manage playbook execution, inventories, credentials, scheduling, and role-based access control through a central dashboard rather than running Ansible from individual command lines.

Operations teams and DevOps engineers who run Ansible at scale across multiple environments and team members benefit most. AWX adds the collaboration, scheduling, and auditing layers that raw Ansible CLI lacks.

How it saves time or tokens

AWX centralizes Ansible automation management. Instead of each engineer running playbooks from their laptop with different inventory files and variable overrides, AWX provides a single source of truth. Job templates define exactly what runs, against which inventory, with which credentials. The REST API enables integration with CI/CD pipelines, ticketing systems, and monitoring tools. Scheduled jobs and webhook triggers automate recurring tasks without manual intervention.

How to use

1. Deploy AWX using the AWX Operator on Kubernetes:

# Install the AWX Operator
kubectl apply -f https://raw.githubusercontent.com/ansible/awx-operator/main/deploy/awx-operator.yaml

# Create an AWX instance
cat <<EOF | kubectl apply -f -
apiVersion: awx.ansible.com/v1beta1
kind: AWX
metadata:
  name: awx
spec:
  service_type: nodeport
EOF

1. Access the web UI at the NodePort address and log in with the admin credentials.

1. Create a Project (Git repo with playbooks), Inventory, Credential, and Job Template to start running automation.

Example

# Trigger a job template via REST API
curl -X POST https://awx.example.com/api/v2/job_templates/5/launch/ \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"extra_vars": {"env": "production", "version": "2.1.0"}}'

# Check job status
curl https://awx.example.com/api/v2/jobs/42/ \
  -H 'Authorization: Bearer YOUR_TOKEN'

Related on TokRepo

• DevOps Tools -- Infrastructure automation and deployment tools
• Self-Hosted Solutions -- Self-hosted automation platforms

Common pitfalls

• AWX requires Kubernetes for deployment (via the AWX Operator). The older Docker Compose method is deprecated. Plan for a K8s cluster or use K3s for lightweight setups.
• AWX is the upstream project and moves faster than the commercial Ansible Automation Platform. Expect more frequent updates and occasional breaking changes.
• Resource requirements are significant. AWX needs at least 4GB RAM and 2 CPU cores for the Kubernetes pods. Large inventories and concurrent jobs require more.