ansible-core is the successor to the "batteries included" ansible CLI package prior to Ansible 2.10, minus most of the modules that were split into collections.

AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It's the upstream of automation controller (formerly Ansible Tower). Both are upstream projects for Red Hat Ansible Automation Platform.

AWX

What is The AWX Project?

The AWX project—AWX for short—is an open source community project, sponsored by Red Hat®, that enables users to better control their community Ansible project use in IT environments. AWX is the upstream project from which the automation controller (formerly Ansible Tower) component in Red Hat Ansible Automation Platform is ultimately derived.

Why is Red Hat doing this?

Open sourcing everything is what Red Hat does. When Ansible®, Inc. was acquired by Red Hat, we told our users that we would open the source code for Ansible. The AWX project is a fulfillment of that intent.

More importantly, the Ansible team—like all of Red Hat—believes deeply in the power of community-driven innovation. The Ansible project itself has more than 5,000 contributors, and we believe this will continue to grow and expand. Many of the critical features we now provide for users and customers were built almost entirely by the Ansible community. We believe that the open source model has brought many innovations to the AWX Project.

Learn more about Red Hat Ansible Automation Platform, the subscription-based, supported enterprise product

What’s the difference between AWX and automation controller?

AWX is designed to be a frequently released, fast-moving project where all new development happens.

Automation controller is produced by taking selected releases of AWX, hardening them for long-term supportability, and making them available to customers as a hosted service within Red Hat Ansible Automation Platform. Ansible Automation Platform is fully supported by Red Hat, while AWX is supported by the community.

This is a tested and trusted method of software development for Red Hat, which follows a similar model to Fedora and Red Hat Enterprise Linux®.

Learn more about the differences between AWX and Red Hat Ansible Automation Platform

Where can I find support for AWX?

The community can help answer questions about AWX via the Ansible Community Forum and Matrix. You can also file bug reports or contribute bug fixes in the AWX GitHub repository.

Because AWX is designed to be a rapidly moving project, Red Hat does not provide any paid support for it. For a fully supported automation management platform, read more about Red Hat Ansible Automation Platform.

Can I upgrade from one version of AWX to another?

Upgrading of AWX is only available for the awx-operator (Kubernetes) based install. For upgrading awx-operator from version 0.18 or above, follow the instructions in this document. Direct, in-place upgrades between prior AWX versions are not supported.

Under which open source license is AWX available?

The AWX source code is available under the Apache License 2.0.

How can I get involved with the AWX Project?

The AWX Project is hosted on GitHub. We welcome community contributions. Read the contributor guide. Join the Ansible Community Forum.

Where do I report an AWX bug?

The AWX project uses GitHub for its issue tracking. You can file your issues on this page.

How often is AWX released?

The AWX team currently plans to release new builds approximately every 2 weeks. The AWX team will flag certain builds as “stable” at their discretion. Note that the term “stable” does not imply fitness for production usage or any kind of warranty.

What is the governance structure of the AWX project?

For now, the Red Hat sponsored AWX team will continue to make the majority of decisions for the AWX project, with input from the community. Over time, the team will evaluate its governance structure and choose a structure that balances community needs with product needs.

If my software runs with AWX, can I say that it is certified to run on AWX or on Red Hat Ansible Automation Platform?

No. Only Red Hat has the ability to say that software is “certified,” although you may truthfully use the AWX name to describe the relationship between your software and AWX. For more details, consult the AWX trademark guidelines.

I want to build my own forked version of AWX. Can I call it AWX? Can I call it Red Hat Ansible Automation Platform?

No. You may fork AWX like any open source codebase, but you may not use Red Hat trademarks. Red Hat reserves the exclusive right to decide what products can bear those marks. Be sure to read the AWX trademark guidelines for more information.

Will contributions to AWX require a “Contributor License Agreement”?

No. However, all contributions to AWX will require agreement with the Developer Certificate of Origin (DCO) at the time of submission. The text of the DCO can be read in full at developercertificate.org.

Does Red Hat recommend AWX for production environments?

No.

Does Red Hat’s Open Source Assurance Program apply to AWX?

No.

Ansible Community

How can I contribute back to the user ecosystem?

We are pleased to shared there are so many ways to contribute to the Ansible ecosystem. Here are just a few examples:

Organize meetups with other automation enthusiasts
Present at conferences about Ansible
Host Ansible workshops
Share content on Galaxy
Code a new module or collection
Report or fix a bug
Improve the documentation

Want to get involved? Check out our contributor resources or chat with other users - we'd love to have you.

Where can I find the blogs once on Ansible.com?

Click here to find the blog archive from Ansible.com.