Red Hat Ansible Automation Platform Self-Managed

Enterprise IT automation platform installed and managed by the customer in a public-cloud environment.

3 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Containerized installer on RHEL with Podman or the OpenShift Operator

  2. Operated by

    Your team

    Customer manages the platform, execution capacity, infrastructure, secrets, backups and upgrades; Red Hat supplies subscribed software updates and support.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodContainerized installer on RHEL with Podman or the OpenShift Operator
InfrastructureServers / containers
Self-managed Ansible Automation Platform uses persistent RHEL containers or customer-operated OpenShift workloads with databases and execution capacity.
Licensing modelCommercial Only
The selected Red Hat Ansible Automation Platform requires a commercial subscription and valid manifest. Upstream Ansible Core and AWX do not change this enterprise product's license classification.
LicenseCommercial Red Hat Ansible Automation Platform subscription required.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

12 of 12 fields researched (100%) · 7 documented · 5 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
Not confirmedEvidence and scope for Marketplace delivery

AWS lists Red Hat subscriptions including AAP, alongside a different managed AAP service. Confirm an offer/order explicitly entitling this self-managed 2.7 installation.

Reviewed public evidence for Red Hat Ansible Automation Platform Self-Managed; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility

Managed AAP Marketplace committed-spend claims do not establish treatment of this self-managed subscription. Obtain the selected offer and buyer-agreement eligibility.

Reviewed public evidence for Red Hat Ansible Automation Platform Self-Managed; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Single sign-on
AvailableEvidence and scope for Single sign-on

AAP 2.7 documents SAML identity-provider configuration through platform gateway. External authentication must use the gateway; legacy direct component authentication is no longer supported.

Self-managed AAP 2.7 platform gateway · Source ↗ · Mandatory gateway authentication ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

SCIM provisioning
Not confirmedEvidence and scope for SCIM provisioning

Platform gateway documents SAML/LDAP/OIDC and group/role mapping, but a supported AAP 2.7 SCIM lifecycle endpoint was not established.

Reviewed public evidence for Red Hat Ansible Automation Platform Self-Managed; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Compliance attestations
Not confirmedEvidence and scope for Compliance attestations

The reviewed Red Hat Ansible Automation Platform Self-Managed material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage.

Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

AAP 2.7 centralizes external authentication at platform gateway and documents HTTPS redirects and CSRF settings. Restrict component access and configure the chosen identity provider and role mappings.

AAP 2.7 gateway and deployment configuration · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Air-gapped operation
AvailableEvidence and scope for Air-gapped operation

The containerized installer supports disconnected installation using a downloaded setup bundle, local RHEL RPM repositories and bundle_install=true. Required metrics service works without internet access; content and update transfers remain operator responsibilities.

AAP 2.7 containerized disconnected installation · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The subscription-gated containerized setup bundle uses a configured inventory to install platform components with Podman; OpenShift uses the supported Operator path. AAP 2.7 does not use the removed RPM installer.

AAP 2.7 installation methods; not AWX or Ansible Core · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The containerized system requirements distinguish the supported RHEL host, subscriptions, database and component resources. Use the deployment-model inventory and execution capacity to size each host; portal-only appliance requirements do not size the complete platform.

AAP 2.7 containerized topology, not portal-only sizing · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The selected Red Hat Ansible Automation Platform requires a commercial subscription and valid manifest. Upstream Ansible Core and AWX do not change this enterprise product's license classification.

Red Hat Ansible Automation Platform Self-Managed: software entitlement and edition boundary; infrastructure and operating costs are separate · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate

Choose the supported HA inventory and count managed nodes, execution jobs, execution environments, controller/hub/database hosts and RHEL/AAP subscriptions. Human users and data size alone do not size automation capacity. A complete monthly operating estimate is not established.

Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

The reviewed self-managed documentation is the AAP 2.7 line, with separate patch-release notes and component updates. Select a supported patch and matching bundle; this is a version-line review, not a claim about a latest patch timestamp.

Self-managed AAP documentation line and patch index · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Scope & considerations

This entry covers Red Hat Ansible Automation Platform, not the managed cloud service and not upstream Ansible Core or AWX. Current 2.7 deployment models use the containerized RHEL installer or OpenShift Operator; the RPM installer was removed in 2.7. Validate supported RHEL or OpenShift versions, execution environments and subscription manifests before installation.

Category fit

DevOps
Enterprise configuration, provisioning and operations automation across infrastructure and applications.
Workflow automation
Controller, event-driven automation and reusable automation content coordinate governed operational workflows.

Compare within DevOps

  • Argo CDGitOps continuous delivery controller and interface for deploying and reconciling applications in Kubernetes clusters.
    • AWS
    Customer-operated · Open Source / Open Core
  • Azure DevOps ServerSource control, CI/CD, work tracking, testing and package management installed on Azure virtual machines you operate.
    • Azure
    Customer-operated · Commercial Only
  • Bitbucket Data CenterCommercial self-managed Git collaboration and code-review platform for eligible existing Atlassian customers, with an announced Hybrid License transition.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • CircleCI ServerCommercial self-hosted CI/CD platform installed in a customer-operated Amazon EKS or Google GKE cluster.
    • AWS
    • Google Cloud
    Customer-operated · Commercial Only
  • CloudBees CI on Modern Cloud PlatformsEnterprise continuous-integration platform installed with Helm in a Kubernetes cluster you operate.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • GitHub Enterprise ServerCustomer-operated GitHub software-development platform deployed as a licensed virtual appliance.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • GitLab Self-ManagedSource control and CI/CD on infrastructure you operate.
    • AWS
    • Azure
    • Google Cloud
    • Oracle Cloud
    • Alibaba Cloud
    Customer-operated · Open Source / Open Core
  • HarborContainer and OCI artifact registry for managing software images within customer-operated infrastructure.
    • Railway
    Customer-operated · Open Source / Open Core

Showing 8 of 27 other listings in DevOps. These products address related workflows; read their category-fit notes before comparing scope. See all of DevOps →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Self-managed Ansible Automation Platform in named public clouds ↗ · AWS, Azure, Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

      Red Hat documents self-managed Ansible Automation Platform deployments on infrastructure hosted in AWS, Azure and Google Cloud. The customer operates the RHEL or OpenShift environment and supplies the subscription.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory