Projects, Inventories & Job Templates

AWX models your automation with three building blocks: a project, an inventory and a job template. Wire them together and you can run anything.

A project tells AWX where your playbooks live, usually a Git repository. AWX clones it and refreshes when you sync. 📁

Hit Sync on a project and AWX fetches the newest commits. You can also auto-sync on launch so jobs always run current code.

An inventory in AWX is the same idea as a CLI inventory: the hosts and groups a job can target, managed through the UI or imported.

You can type hosts in by hand or attach an inventory source, like AWS or a Git file, so AWX refreshes the host list automatically.

A job template is the saved recipe: it binds one project, one playbook, one inventory and credentials into a reusable, launchable unit. 🎯

Inside the template you choose exactly which playbook file from the project runs. One project can power many templates.

The template references stored credentials so AWX knows how to SSH in and become root, without secrets ever living in your code.

Clicking Launch queues a job. AWX streams live, color-coded output so the whole team can watch the play unfold in real time. 👀

Each launch becomes a job record with full output, timing and status kept forever, giving you an audit trail no terminal ever did.

Mark fields like inventory or limit as prompt on launch and AWX asks for them each run, making one template flexible across many scenarios.

Which object actually ties a playbook to an inventory so it can run?

Projects bring your code, inventories list your hosts, and job templates fuse them with credentials into one-click, fully logged automation. ✅