What's New in AAP 2.5 — Ansible Automation Platform Features

Introduction

Ansible Automation Platform (AAP) 2.5 is the latest enterprise release from Red Hat, building on the platform's shift to a container-native, event-driven architecture. This guide covers the key features and what they mean for enterprise automation teams.

AAP 2.5 Architecture

┌─────────────────────────────────────────────┐
│           Ansible Automation Platform 2.5    │
│                                              │
│  ┌──────────┐  ┌──────────┐  ┌───────────┐ │
│  │Automation│  │ Event-   │  │ Ansible   │ │
│  │Controller│  │ Driven   │  │ Lightspeed│ │
│  │          │  │ Ansible  │  │ (AI)      │ │
│  └──────────┘  └──────────┘  └───────────┘ │
│                                              │
│  ┌──────────┐  ┌──────────┐  ┌───────────┐ │
│  │Automation│  │ Execution│  │ Private   │ │
│  │  Hub     │  │Environ-  │  │ Automation│ │
│  │          │  │ ments    │  │   Hub     │ │
│  └──────────┘  └──────────┘  └───────────┘ │
│                                              │
│  ┌──────────────────────────────────────┐   │
│  │    Ansible Automation Mesh           │   │
│  │    (Distributed execution layer)     │   │
│  └──────────────────────────────────────┘   │
└─────────────────────────────────────────────┘

Key Features

1. Enhanced Event-Driven Ansible (EDA)

Event-Driven Ansible processes events from external systems and triggers automation in response.

# EDA rulebook example — auto-remediate disk full
---
- name: Disk space remediation
  hosts: all
  sources:
    - ansible.eda.alertmanager:
        host: 0.0.0.0
        port: 5000

  rules:
    - name: Disk space critical
      condition: event.alert.labels.alertname == "DiskSpaceCritical"
      action:
        run_job_template:
          name: "Cleanup Disk Space"
          organization: "Operations"
          job_args:
            extra_vars:
              target_host: "{{ event.alert.labels.instance }}"
              threshold: "{{ event.alert.labels.threshold }}"

    - name: Service down
      condition: event.alert.labels.alertname == "ServiceDown"
      action:
        run_job_template:
          name: "Restart Service"
          organization: "Operations"
          job_args:
            extra_vars:
              service_name: "{{ event.alert.labels.service }}"
              target_host: "{{ event.alert.labels.instance }}"

What's new in 2.5:

Improved event filtering and throttling
Better integration with ServiceNow, PagerDuty, Dynatrace
Event-driven credential rotation
Audit trail for all event-triggered actions

2. Ansible Lightspeed AI

# AI-assisted automation in AAP 2.5:
# - Natural language → playbook generation
# - Context-aware suggestions (knows your inventory/roles)
# - Intelligent error diagnosis from job logs
# - Recommended remediation actions
# - Model Context Protocol (MCP) integration

Enterprise features:

On-premises model deployment (IBM watsonx)
Custom model fine-tuning on your playbooks
RBAC for AI features
Telemetry opt-out for air-gapped environments

3. Execution Environments 2.0

# execution-environment.yml improvements
version: 3

dependencies:
  galaxy: requirements.yml
  python: requirements.txt
  system: bindep.txt

images:
  base_image: registry.redhat.io/ansible-automation-platform/ee-minimal-rhel9:latest

options:
  package_manager_path: /usr/bin/microdnf

additional_build_steps:
  append_final:
    - LABEL ansible.version="2.20"
    - HEALTHCHECK CMD ansible --version

What's new:

Smaller base images (minimal variants)
Multi-architecture builds (amd64 + arm64)
Built-in security scanning
Version pinning improvements

4. Automation Mesh Improvements

# Automation Mesh distributes execution across locations
# What's new in 2.5:
# - Hop nodes for network-restricted environments
# - Improved connection resilience
# - Automatic failover between execution nodes
# - Bandwidth optimization for large inventories

Corporate HQ               DMZ                Data Center
┌──────────┐         ┌──────────┐         ┌──────────┐
│Controller│ ──────► │ Hop Node │ ──────► │Exec Node │
│          │         │          │         │          │
└──────────┘         └──────────┘         │ ┌──────┐ │
                                          │ │Server│ │
                                          │ │Server│ │
                                          │ │Server│ │
                                          └─┘──────┘─┘

5. Private Automation Hub

# Curated content management for your organization
# What's new:
# - Improved collection signing and verification
# - Namespace management per team
# - Sync from certified + community sources
# - Collection dependency resolution improvements
# - Container registry for Execution Environments

Migration from AAP 2.4

# Key migration considerations:
# 1. Execution Environments — rebuild with v3 format
# 2. EDA rulebooks — update to new event source plugins  
# 3. Automation Mesh — update receptor configuration
# 4. Collections — verify compatibility with ansible-core 2.20

# Pre-migration checklist:
- name: Verify AAP 2.5 compatibility
  tasks:
    - Check ansible-core version requirements (2.20+)
    - Audit installed collections for compatibility
    - Test Execution Environments with new base images
    - Review EDA rulebooks for deprecated event sources
    - Backup Controller database and configuration
    - Test upgrade in staging environment first

AAP 2.5 vs AWX

Feature	AAP 2.5	AWX (Community)
Support	✅ Red Hat subscription	❌ Community only
Lightspeed AI	✅ Included	❌ Not available
EDA	✅ Full integration	⚠️ Separate project
Automation Hub	✅ Private Hub + certified content	❌ Galaxy only
Automation Mesh	✅ Full	❌ Not available
FIPS compliance	✅ Certified	❌ Not certified
Pricing	Per-node subscription	Free

Getting Started with AAP 2.5

# Option 1: OpenShift deployment (recommended)
# Install AAP Operator from OperatorHub

# Option 2: RPM-based on RHEL 9
sudo subscription-manager repos --enable ansible-automation-platform-2.5-for-rhel-9-x86_64-rpms
sudo dnf install automation-controller
sudo automation-controller-installer

# Option 3: Developer trial
# https://www.redhat.com/en/technologies/management/ansible/trial

Conclusion

AAP 2.5 strengthens three pillars: AI (Lightspeed with MCP for context-aware assistance), events (EDA with better integrations and throttling), and scale (Automation Mesh with hop nodes and failover). For enterprises, the combination of AI-assisted playbook creation, event-driven remediation, and distributed execution represents the most capable automation platform available. Start with the developer trial to evaluate before committing to a subscription.