AAP 2.7 Upgrades for Managed Cloud Customers
Introduction
In June 2026, Ansible Automation Platform version 2.7 will be released. Managed AAP instances will be upgraded following the release of 2.7.
This article will be a guide for Ansible Automation Platform on Microsoft Azure and Ansible Automation Platform Service on AWS customers to navigate the upgrade process. Red Hat will use this article to communicate the timeline of the upgrade process, actions that customers need to take if they arise, and changes that need to be considered.
Further details regarding the upgrade will be added to this article as information becomes available. We recommend that all Ansible Automation Platform customers follow this article so that you can be automatically notified when new changes and updates are made.
Choose your upgrade window
You may select the upgrade window for your current Ansible Automation Platform deployments. Use this Content from docs.google.com is not included.form to notify the product team of your preference upgrade windows. Currently two upgrade segments (at regular maintenance times) are available:
- June 2nd, 2026
- June 16th, 2026
If you do not choose any of the upgrade segment, ALL existing managed AAP deployments will be upgraded on June 16th, 2026. Customers will have until May 22, 2026 to select an upgrade window.
Please submit one entry for each deployment that your organization has.
Questions
If you have any questions or feedback about the upgrade process, then you may inform your account team, or submit a notice in this Content from docs.google.com is not included.form to notify Ansible Automation Platform Product Management of your question.
Changes
The following changes are only applicable to Ansible Automation Platform on Microsoft Azure customers. Customers on Ansible Automation Platform Service on AWS do not need to make this change as this is already reflected on your AAP deployments.
| Change/Feature | Description |
|---|---|
| Single API Ingress | In AAP 2.5, platform gateway was introduced to unify access to all platform components. In Red Hat Ansible Automation Platform 2.7, platform gateway is the only supported method for external access to platform components. Direct API access (ingress) to automation controller, automation hub, and event-driven ansible will be removed. Existing URL paths for automation controller and private automation hub if active will not function after AAP 2.7 upgrade. Customers should move to new API paths exposed via the platform URL/ingress. Old URLs (Eg: controller.example.com , hub.example.com, eda.example.com ) will be through the New URL This content is not included.https://platform.instance-id.ansiblecloud.redhat.com/ |
URL Conversion Pattern Rule
| Component | Legacy URL Pattern (2.6) | Gateway URL Pattern (2.7) |
|---|---|---|
| Controller Jobs | /api/v2/jobs/ | /api/controller/v2/jobs/ |
| Controller Templates | /api/v2/job_templates/ | /api/controller/v2/job_templates/ |
| Hub Collections | /api/galaxy/v3/collections/ | /api/galaxy/v3/collections/ |
| EDA Activations | /api/eda/v1/activations/ | /api/eda/v1/activations/ |
Rule: Insert /api/{component}/ before the legacy path.
Customer Actions
Red Hat intends to limit the need for customer actions required as part of the upgrade. However, due to some fundamental changes to Ansible Automation Platform, the following must be completed by customers prior to or during the upgrade process.
The following actions are only applicable to Ansible Automation Platform on Microsoft Azure customers.
| Actions | Description/Activities | Complete By |
|---|---|---|
| Single API Ingress | If you are using controller(controller.example.com) and hub (hub.example.com)API endpoints and URLs , these will not be functional in AAP 2.7. Customers that have API integrations will need to migrate to the new platform gateway API (https://platform.instance-id.ansiblecloud.redhat.com) endpoints in order to avoid future disruption to those integrations. If you do not have this information, you can submit a Support Ticket to the Red Hat SRE team to request the list of active endpoints accessing these URLs. | Any time prior to upgrade |
Timeline
| Date | Event |
|---|---|
| Mar 23, 2026 | Customer communication regarding Ansible Automation Platform upgrades to 2.7 begins. |
| June 2, 2026 | Segment 1 Managed AAP Deployment Upgrades |
| June 3, 2026 | AAP 2.7 Upgrade is made generally available. |
| June 16, 2026 | Segment 2 Managed AAP Deployment Upgrades |