AAP 2.6 vs 2.5 Architecture: Complete Platform Comparison (2026)

AAP 2.5 introduced the platform gateway — the unified entry point that fundamentally changed how AAP components interact. AAP 2.6 builds on that foundation with three major new platform services (automation dashboard, self-service portal, Lightspeed assistant) plus significant changes to deployment models, APIs, and Configuration as Code. Here's every architectural difference.

Platform Services: 2.5 vs 2.6

What 2.5 Introduced (Still in 2.6)

AAP 2.5 was the architectural pivot — it added the platform gateway as a unified front end that sits in front of all other services:

                    ┌─────────────────────┐
Users/API ────────► │  Platform Gateway   │
                    │  (unified auth,     │
                    │   RBAC, routing)    │
                    └──────┬──────────────┘
                           │
              ┌────────────┼────────────┐
              ▼            ▼            ▼
     ┌────────────┐ ┌──────────┐ ┌─────────┐
     │ Controller │ │   Hub    │ │   EDA   │
     └────────────┘ └──────────┘ └─────────┘

Key 2.5 changes that carry forward:

• Centralized authentication through the gateway
• Unified RBAC across all components
• Single URL entry point for the entire platform
• Gateway API (/api/gateway/v1/)

What 2.6 Adds

AAP 2.6 adds three new services on top of the 2.5 gateway architecture:

                    ┌─────────────────────────────┐
Users ────────────► │       Platform Gateway       │
                    └──────┬──────────────────────┘
                           │
     ┌──────────┬──────────┼──────────┬───────────┐
     ▼          ▼          ▼          ▼           ▼
┌─────────┐┌────────┐┌─────────┐┌──────────┐┌──────────┐
│Dashboard ││Lightsp.││Self-Svc ││Controller││   Hub    │
│(NEW)     ││Assist. ││Portal   ││          ││          │
│          ││(NEW)   ││(NEW)    ││          ││          │
└─────────┘└────────┘└─────────┘└──────────┘└──────────┘
                                      │           │
                                 ┌────┘     ┌─────┘
                                 ▼          ▼
                            ┌─────────┐┌────────┐
                            │   EDA   ││ Redis  │
                            └─────────┘└────────┘

Component-by-Component Comparison

Platform Gateway

Automation Controller

Automation Hub

Event-Driven Ansible (EDA)

User Interface

Deployment Architecture Changes

Installation Methods

OS Support

Tested Topologies

Both versions offer growth and enterprise topologies. The key change: AAP 2.6 provides improved, opinionated reference architectures with clearer documentation and simplified inventory files.

Database Requirements

API Changes

Environment Variable Standardization

AAP 2.5 used component-specific prefixes:

# AAP 2.5
CONTROLLER_HOST=https://controller.example.com
CONTROLLER_USERNAME=admin
CONTROLLER_PASSWORD=secret
HUB_HOST=https://hub.example.com
EDA_HOST=https://eda.example.com

AAP 2.6 standardizes to a single prefix:

# AAP 2.6
AAP_HOST=https://gateway.example.com
AAP_USERNAME=admin
AAP_PASSWORD=secret

Backward compatibility: Component-specific variables still work but are deprecated.

Configuration as Code

AAP 2.6 ships with enhanced ansible.platform collection for managing all AAP components:

# AAP 2.6 CaC approach
- name: Configure AAP via gateway API
  hosts: localhost
  collections:
    - ansible.platform

  tasks:
    - name: Create organization
      ansible.platform.organization:
        name: "Engineering"
        state: present

    - name: Create team
      ansible.platform.team:
        name: "DevOps"
        organization: "Engineering"

    - name: Create project
      ansible.platform.project:
        name: "Infrastructure"
        organization: "Engineering"
        scm_type: git
        scm_url: "https://github.com/org/infra-playbooks.git"

Service Accounts

New in 2.6 — non-human identities for CI/CD and API integrations:

- name: Create service account
  ansible.platform.service_account:
    name: "ci-pipeline"
    description: "Jenkins CI integration"
    organization: "Engineering"

See also: Install Ansible Automation Platform in Red Hat Ansible OpenShift Platform operator via Operator

Technology Preview in 2.6

Upgrade Path: 2.5 → 2.6

Since AAP 2.5 already has the platform gateway, upgrading to 2.6 is simpler than upgrading from 2.4:

1. Update environment variables from CONTROLLER_/HUB_/EDA_ to AAP_
2. Configure new services (dashboard, self-service portal, Lightspeed)
3. Update external integrations to use gateway API

FAQ

Is the 2.5 → 2.6 upgrade disruptive?

Minimal disruption. Since 2.5 already introduced the gateway architecture, 2.6 is an incremental upgrade. The new services (dashboard, portal, Lightspeed) are additive — they don't change existing functionality.

Do I need to change my playbooks when upgrading to 2.6?

No. The default execution environment still uses ansible-core 2.16. Your existing playbooks continue working unchanged. The optional ansible-core 2.18 EE is available for testing newer features.

What's the biggest architectural difference between 2.5 and 2.6?

AAP 2.5 was the foundational architecture change (introducing the gateway). AAP 2.6 is about expanding services on that foundation — adding analytics (dashboard), GenAI (Lightspeed), and self-service capabilities (portal) without changing the core architecture.

Can I run 2.6 without the new services?

Yes. The automation dashboard, Lightspeed assistant, and self-service portal are optional. Your existing controller, hub, and EDA workflows work the same without enabling them.

When should I migrate from RPM to containerized?

Now. AAP 2.6 is the last version with RPM support. Start planning your migration immediately — AAP 2.7 will only support containerized and OpenShift deployments.

Conclusion

AAP 2.6 is an evolutionary release that adds three new services on top of the 2.5 gateway architecture: automation dashboard for ROI measurement, Lightspeed assistant for AI-powered support, and self-service portal for scaling automation to non-Ansible users. The core architecture remains the same, making 2.5 → 2.6 a smooth upgrade. The most urgent action is migrating from RPM to containerized — 2.6 is your last chance.

See also: AAP 2.6 Tested Deployment Models: Growth & Enterprise Topologies Guide

Related Articles

• AAP 2.6 Install Guide
• AAP 2.6 Upgrade Guide
• AAP 2.6 Tested Deployment Models
• What's New in AAP 2.6
• AAP 2.6 Self-Service Portal
• AAP 2.6 Automation Dashboard
• AAP 2.6 Lightspeed Assistant