RPM to Managed Ansible Automation Platform migration prerequisites

Before migrating from an RPM-based deployment to a Managed Ansible Automation Platform deployment, ensure you meet the following prerequisites:

Note:
Completing this migration is a required step if you plan to upgrade to Ansible Automation Platform 2.7. RPM-based deployments are not supported as an upgrade path to 2.7.
  • You have a source RPM-based deployment of Ansible Automation Platform.
  • The source deployment must be on the same major version as the Managed Ansible Automation Platform offering, and must be on the latest async/patch release of that version.
    • Determine the Managed AAP version: Check the 2.7 Release Notes or contact Red Hat Support to confirm the current version deployed in Managed Ansible Automation Platform.
    • Upgrade your source if needed: If your source is on an older major version (e.g., 2.4 or 2.5), you must upgrade to match the Managed Ansible Automation Platform version, for example, 2.7, before migrating.
    • Apply the latest patches: Ensure your source is on the latest async/patch release, for example, 2.7.3, not 2.7.0.
    • Why this matters: Migration uses a database dump-and-restore process that requires version parity. Cross-version migrations are not supported.
  • You have a target Managed Ansible Automation Platform deployment.
  • You have enabled local authentication on the source deployment before the migration.
  • A local administrator account must be functional on the source deployment before migration. Verify this by performing a successful login to the source deployment.
  • You have a plan to retain a backup throughout the migration process and to ensure that your existing Ansible Automation Platform deployment remains active until your migration has completed successfully.
  • You have a plan for any environment changes based on the migration from a self-hosted Ansible Automation Platform deployment to a Managed Ansible Automation Platform deployment:
    • Job log retention changes from a customer-configured option to 30 days.
    • Network changes occur when moving the control plane to the managed service.
    • Automation mesh requires reconfiguration.
  • You must reconfigure or re-create Single Sign-On (SSO) identity providers post-migration to account for URL changes.