Automation Platform
-
Overview Get started
Features
- Automation coding assistant
- Automation intelligent assistant
- Ansible plug-ins for Red Hat Developer Hub
- Event-Driven Ansible
- Self-service automation portal
- Automation execution environments
- Automation controller
- Automation mesh
- Ansible Content Collections
- Ansible automation hub
- Automation dashboard and automation analytics
- Ansible development tools
-
All features
-
Use cases -
Integrations Extend your use of Ansible Automation Platform with partner offerings, including certified collections and resources.
-
Deployment options - Documentation
Upgrade Red Hat Ansible Automation Platform
Upgrading to a newer version of Red Hat® Ansible® Automation Platform doesn’t have to be disruptive to business as usual. Our resources, tools, and consulting can help you plan your upgrade to take full advantage of the latest capabilities while maintaining your system’s stability.
Plan for the next generation of IT automation
Our latest release delivers new features, platform enhancements, and strategic integrations that will help you continue to build a resilient, trusted foundation for the next generation of IT operations. Upgrading to the latest version of Ansible Automation Platform helps you stay aligned with these innovations while simplifying future upgrades.
Note: Ansible Automation Platform 2.4 reaches end of Maintenance Support on June 30, 2026. There is no direct upgrade path from 2.4 to Ansible Automation Platform 2.7 or later versions.
Start your upgrade
Our official product documentation for Ansible Automation Platform 2.7 provides an installation guide to help you get up and running. This guide provides a detailed overview of the changes and improvements in the upgrade process to Ansible Automation Platform 2.7, including new infrastructure requirements, data migration specifics, and a comparison of different deployment types. It addresses frequently asked questions and outlines how existing authentication and user data are handled during the upgrade.
Migrate vs. upgrade
Before you get started, it’s important to understand the difference between a migration and an upgrade.
Migrate
Migrations involve changing the installation type—for example, moving from an RPM-based to a container-based installation—or updating the underlying version of Red Hat Enterprise Linux®. This option requires a backup and restore procedure.
Upgrade
Upgrades are application actions, such as changing versions of Ansible Automation Platform from 2.6 to 2.7.
For Ansible Automation Platform 2.5 and earlier, you must first migrate or upgrade to Ansible Automation Platform 2.6 before upgrading to 2.7.
Choose your upgrade deployment type
Start with these tested deployment models to ensure a smoother transition.
Container-based
Explore containerized options for Red Hat Enterprise Linux 9 or 10 and Red Hat OpenShift® Container Platform.
Red Hat OpenShift Container Platform
Understand the tested and supported options available for running Ansible Automation Platform on Red Hat OpenShift.
Not sure which deployment type is right for your enterprise?
Get expert help
Ready to accelerate your move to the latest version of Ansible Automation Platform?
Our Red Hat consultants can help you navigate the complexities and ease your stress while ensuring a resilient foundation for your automation.
Advantages of upgrading
Starting your journey now helps you improve productivity and efficiency with your existing automation investment, while maintaining platform performance and reliability.
Unlock more value and productivity
Our latest innovations—including AI-enabled features, self-service guided workflows, MCP server, partner integrations, and more—are only available in the latest release. Give your teams access to tools that make automation easier to create, manage, and scale.
Optimize event-driven automation workflows
The more time that passes between upgrades, the more complex the migration process. Staying current makes your journey simpler and more straightforward, and helps you reduce downtime and service interruptions.
Access an improved user experience
Every release hardens the platform with patched vulnerabilities, updated security features, and tighter access controls. Lagging behind means accumulating exposure that becomes harder to remediate over time.
FAQs
What if I can’t complete my upgrade from Ansible Automation Platform 2.4 before June 30, 2026?
Contact your account team to explore Extended Lifecycle Support (ELS) options to ensure continuity and coverage.
What if I'm moving from AWX or an older version of Ansible Automation Platform i.e., older than 2.4?
If you’re moving from AWX, you will need to install Ansible Automation Platform 2.7. If you're moving from an older version of the platform, you will need to upgrade to 2.6, then upgrade to 2.7. Note that in some cases, a migration to a new operating system or topology may also be required. Read our installation guide.
When moving from using RPM to containerized installations, do I need three separate VMs for service containers (automation controller, database, and automation hub)?
Yes, we still recommend having one VM instance for each service container. See the installation guide and upgrade guide mentioned above. There are additional changes, so be sure to review the tested deployment models.
How is the database migration handled from Ansible Automation Platform 2.4 to 2.6? Should the database be migrated as well?
Upgrading from Ansible Automation Platform 2.4 to 2.6 handles the change of the database. After performing an upgrade, you can then migrate to a different installation topology.
Additional resources
What's new with Ansible Automation Platform 2.7
Get informed about Ansible Automation Platform’s latest release.
Pre-upgrade migration checklist
What you need to know before upgrading to Ansible Automation Platform 2.7.
