Maintenance and Feature Updates
The Site Reliability Team performs regular maintenance on the managed service control plane for our Red Hat Ansible Automation Platform Service on AWS customers. This process is part of the managed service value add we provide to our customers. SRE team provides customers with a secure, performance version of Red Hat Ansible Automation Platform Service on AWS. The table below provides recent maintenance windows and changes that occurred.
Customers may wish to subscribe to notification on this article to stay informed about the maintenance.
For more information on what the latest “Ansible Automation Platform stream release” contains, please reference this documentation.
Note: Customers should periodically review and update their execution environments to ensure they are running recent builds containing performance, security and general bug fixes.
| Date | Description |
|---|---|
| 2026-03-03 | Update: OpenShift Control Plane 4.19.23 |
| 2026-02-10 | Update: Ansible Automation Platform 2.6 Stream Release - 2.6.20260121 |
| 2026-01-13 | Update: Ansible Automation Platform 2.6 Stream Release - 2.6.20260109 |
| 2025-12-15 | Update: Ansible Automation Platform 2.6 Stream Release - 2.6.20251210 |
| 2025-12-08 | Update: Ansible Automation Platform 2.6 Stream Release - 2.6.20251208 |
| 2025-12-02 | Update: Ansible Automation Platform 2.6 Stream Release - 2.6.20251202 |
| 2025-11-25 | Update: Ansible Automation Platform 2.6 Stream Release - 2.6.20251119 |
| 2025-11-18 | Update: Ansible Automation Platform 2.6 Stream Release - 2.6.20251028 |
| 2025-11-03 | Update: Ansible Automation Platform 2.6 Stream Release - 2.6.20251024 |
| 2025-10-20 | Update: Ansible Automation Platform 2.6 Stream Release - 2.6.20251016 |
| 2025-10-13 | Update: Removal of deprecated parameter |
| 2025-10-06 | Update: Ansible Automation Platform 2.6 Stream Release Early Access - 2.6.20251006 |
| 2025-09-29 | Upgrade: OpenShift Node Pool Version 4.17.37 |
| 2025-09-16 | Update: Ansible Automation Platform 2.5 Stream Release - 2.5.20250916 Upgrade: OpenShift Worker Node Version 4.17.37 |
| 2025-09-09 | Update: Ansible Automation Platform 2.5 Stream Release - 2.5.20250827 Upgrade: OpenShift Control Plane 4.17.37 |
| 2025-08-19 | Update: Ansible Automation Platform 2.5 Stream Release - 2.5.20250730 |
| 2025-08-04 | Update: Ansible Automation Platform 2.5 Stream Release - 2.5.20250702. New AWS Region Enabled |
| 2025-07-21 | Update: Ansible Automation Platform 2.5 Stream Release - 2.5.20250702 |
| 2025-07-08 | Update: Custom Domain/Vanity URL Feature Release |
| 2025-06-30 | Update: Ansible Automation Platform 2.5 Stream Release |
| 2025-06-16 | Update: Ansible Automation Platform 2.5 Stream Release |
| 2025-06-02 | Update: Ansible Automation Platform 2.5 Stream Release |
| 2025-05-12 | Update: Ansible Automation Platform 2.5 Stream Release |
| 2025-05-05 | Update: Ansible Automation Platform 2.5 Stream Release |
| 2025-04-23 | Update: Ansible Automation Platform 2.5 Stream Release |
| 2025-03-25 | Update: Ansible Automation Platform 2.5 Stream Release |
| 2025-03-17 | Update: Ansible Automation Platform 2.5 Stream Release |
| 2025-03-01 | Update: Ansible Automation Platform 2.5 Stream Release |
| 2025-02-25 | Update: Ansible Automation Platform 2.5 Stream Release |
| 2025-02-18 | Update: Ansible Automation Platform 2.5 Stream Release |
| 2025-02-04 | Update: Ansible Automation Platform 2.5 Stream Release |
| 2024-12-16 | Update: Ansible Automation Platform 2.5 Stream Release |
| 2024-11-25 | Update: Ansible Automation Platform 2.5 Stream Release |
| 2024-11-17 | AWS Marketplace offer available as a Private Offer |
(*) Optional features which may incur additional costs are not automatically enabled for existing customers. Customers may contact customer support to request these features to be enabled.
(**) Major software updates to the Ansible Automation Platform are considered new features. The SRE team does not update the execution environments included with the offering Automation mesh execution nodes are designed to minimize the need for patching the execution plane when the control plane is updated. However, future updates to the technology will require customer involvement to update the components in each execution plane node. When patches are needed, customers should follow the process for updating an automation mesh node.
For help with updating your receptor see the Updating Receptors section of the Automation mesh for managed cloud or operator environments guide.
The goal of this policy is to ensure maintenance operations do not impact customer operations with potential breaking changes due to changes in the execution environments.
Comments