Get ready for Ansible Automation Platform 2.7

Red Hat has officially released Ansible Automation Platform 2.7, marking a new milestone in enterprise automation. This latest version is now generally available and brings a host of new features designed to streamline operations and enhance efficiency. A major highlight of Ansible Automation Platform 2.7 is the integration of AI-driven automation tools, which promise to deliver more intelligent and adaptive automation solutions. Additionally, the platform offers a more streamlined developer experience, making it easier for automation content creators to build and deploy their work. Expanded self-service capabilities also empower users to initiate and manage automation tasks more independently. For new installations, Ansible Automation Platform 2.7 has standardized its deployment methods. The containerized installer is now the sole supported method for RHEL, running all platform components as Podman-based rootless containers. This approach supports RHEL 9 (version 9.6 or later) and RHEL 10, ensuring a secure and manageable deployment without requiring root access during operation. The release introduces two primary topology options for containerized deployments: a 'Growth' topology for smaller, all-in-one setups suitable for organizations new to the platform, and an 'Enterprise' topology for larger, multi-VM deployments designed for high-volume automation in production environments. Both topologies utilize PostgreSQL 15 for installer-managed databases, with external databases supporting PostgreSQL 15, 16, or 17. Upgrading to Ansible Automation Platform 2.7 is highly recommended for organizations looking to benefit from the latest security patches, performance improvements, and new features. The upgrade path supports migrations from the latest version of 2.6 to containerized and OpenShift Container Platform deployments. A crucial change for existing users is the deprecation and removal of the RPM-based installer, which means any deployments running on earlier versions or RPM-based installations must first migrate to a supported 2.6 containerized or OpenShift deployment before upgrading to 2.7. Red Hat provides comprehensive documentation and guidance to assist users through the upgrade process, ensuring a smooth transition to the new platform.