Red Hat Ansible Automation Platform — IAC for Business Critical Workflows
Hands-on Red Hat Ansible Automation Platform — enterprise infrastructure as code, with container-based execution, modular workflows and Lightspeed AI.
What a customer gets out of it
- Show automation as an enterprise platform with RBAC, credentials and audit — not a folder of playbooks
- Demonstrate Execution Environments: container-based runs that behave identically everywhere
- Build a modular workflow that chains multiple jobs with conditional branching for a real multi-step task
- Use Ansible Lightspeed to generate and structure automation from natural language, and show what still needs review
- Give customers a defensible answer on automating business-critical systems safely
Why it matters
Most organisations already have Ansible somewhere — usually a directory of playbooks a few people run from their own laptops. That works until the automation touches business-critical systems, at which point the questions become who ran it, against what, with which credentials, and whether it will behave the same next quarter. AAP is the answer to those questions rather than to 'can we automate this': it adds RBAC, credential management, audit and scheduling, and it pins the runtime itself into a container so a playbook cannot drift with whatever happens to be installed on a control node. Lightspeed then changes the economics of getting there, because the bottleneck for most customers is not deciding to automate — it is the backlog of automation nobody has had time to write. This environment lets a customer test all of that against their own use cases.
Lab overview
No walkthrough is recorded for this demo yet, so this is a 21 sec tour of the lab and how to use it.
Trouble playing? Download the file.
Overview
This environment stands up Red Hat Ansible Automation Platform (AAP) in the lab, so customers, SMEs and engineers can drive enterprise automation hands-on — building real workflows against real infrastructure, without touching a production estate.
Bookable as a guided demo, a hands-on POC, or a classroom for a group.
From playbooks to a platform
Nearly every organisation already runs Ansible somewhere. It is usually a directory of playbooks that a handful of engineers run from their own machines, and it works — right up until the automation starts touching business-critical systems.
At that point the questions change. Who ran this, against which hosts, with whose credentials? Can someone run it who is not on the infrastructure team, without handing them root? Will it do the same thing next quarter as it did today? AAP exists to answer those questions. It is the difference between automation as a personal tool and infrastructure as code as an enterprise capability.
The three foundations
- Execution Environments — automation runs inside container images that carry ansible-core, the collections and every dependency together. The runtime is versioned and identical wherever it executes, which is what makes a run predictable: a playbook cannot quietly change behaviour because a control node had a different library installed. It also makes support tractable, because "what was it running" has an exact answer.
- Workflows — real operational tasks are rarely one job. Workflows chain multiple job templates with conditional branching on success, failure or always, so provisioning, configuration, validation and notification compose into one auditable sequence. Each piece stays a small, testable, reusable unit — a modular framework rather than one enormous playbook nobody dares edit.
- Ansible Lightspeed — generative AI that turns a described intent into structured Ansible tasks, following the collections and patterns already in use. The bottleneck for most customers is not deciding to automate; it is the backlog of automation nobody has had time to write. Lightspeed changes that rate, and this demo covers both what it accelerates and what a human still has to review.
What you'll explore
- Automation Controller — job templates, credentials, RBAC, scheduling and the audit trail
- Automation Hub — curated, certified collections instead of whatever was on Galaxy that day
- Event-Driven Ansible — rulebooks that react to events, so automation is triggered by conditions rather than by someone remembering
- Building a workflow end to end and running it against live lab infrastructure
What you'll learn
- Where the line sits between a playbook and a platform, and when an organisation actually crosses it
- How Execution Environments remove the drift that makes automation unpredictable at scale
- Designing modular workflows that survive being maintained by someone else
- What Lightspeed can and cannot be trusted to produce
- How to automate business-critical systems with the controls an audit will ask for