All articles

ansible · awx · aap · satellite

When AWX is no longer enough: moving to Ansible Automation Platform

How an international industrial manufacturer moved from AWX and Foreman to Ansible Automation Platform 2.5 and Red Hat Satellite: design, installation and code refactoring.

By Andrei Tudor Corduneanu 2 min read

In short

  • AWX + Foreman grew without a design: configuration split across two tools.
  • Ansible Automation Platform 2.5 now runs every schedule, job and machine login.
  • Red Hat Satellite only gives hosts content and services without internet access.
  • 1–2 weeks to install. A few weeks to refactor: 1 monorepo → ~20 repositories.
  • 2 people: one Lime engineer, one client engineer.

The starting point: AWX and Foreman, no design

The client, an international industrial manufacturer, manages 500–1,000 virtual machines.

They started automating on their own with AWX and Foreman:

  • Part of the configuration lived in AWX, part in Foreman.
  • No initial design: overlaps and confusion slowed the team down.
  • No vendor support: when the platform broke, patching and provisioning stopped.

Why a supported platform

Two goals:

  • Open a support case when the platform fails at a critical moment.
  • Review the whole design with consultants, not just install new software.

They already relied on Red Hat support for most of their Ansible collections. The platform was the next step.

The new design

One tool per job:

  • Ansible Automation Platform (AAP) 2.5: all schedules, job launches and authentication on the machines.
  • Red Hat Satellite: hosts get content, Red Hat Insights and other services without reaching the internet. No configuration logic.
  • High availability, multi-zone: designed on the client's requirements.

Installation: 1–2 weeks

Firewalls, proxies and machine configuration made the environment complex.

One Lime engineer worked with one client engineer who knew the network and the systems. Installation took 1–2 weeks.

Refactoring the code: a few weeks

We reviewed their Ansible projects together:

  • Monorepo split into ~20 repositories, off a Git server being decommissioned.
  • Playbooks and roles modernized for the latest Ansible versions.
  • Better variables, less code, easier maintenance.
  • A dedicated execution environment.
  • Some workflows redesigned with the team.
  • Inventory as code: Git is the source of the AAP inventory, built dynamically from several sources, including the CMDB.

What AAP adds over AWX

  • Red Hat support and a defined life cycle.
  • Event-Driven Ansible: not included in AWX. We started a feasibility study with the client's monitoring and ITSM platform.
  • Certified content and execution environments in one place.

Results

  • One platform for all automation, with a clear design.
  • Support cases instead of blocked patching.
  • A final report with a Red Hat training plan matched to the team's skills.

Is AWX enough for you?

For a lab or a proof of concept: yes.

When patching and provisioning depend on it, you need support and a design.

Comparing AAP, AWX and Ascender? See the differences and how we work on our Ansible Automation Platform page.

Andrei Tudor Corduneanu

About the author

Andrei Tudor Corduneanu

Red Hat Certified Architect (RHCA) Level II

Founder of Lime. Lives and works in the Linux ecosystem: consultant by day, hands-on engineer always.