Run Ansible Automation Platform across multiple environments

Each Ansible Automation Platform execution step selects its own credential independently. Different steps in the same workflow can connect to different Ansible Automation Platform instances across environments.

Example: Promote a deployment across environments

A single automation orchestrator workflow can coordinate a staged rollout:

  1. The Launch AAP job template step with a development credential runs a deploy template against the development Ansible Automation Platform instance.
  2. The approval step pauses the workflow for a human to verify the development deployment.
  3. The Launch AAP job template step with a production credential runs the same deployment template against the production Ansible Automation Platform instance.

Each step uses a different credential, and each credential points to a different automation controller. The workflow handles the sequencing, gating, and parameter passing between them.

Select credentials dynamically

The Integration field supports expressions. You can resolve the integration at runtime based on upstream output or workflow variables, rather than selecting a fixed integration.

For example, if an upstream step determines the target environment, you can pass the corresponding integration as an expression. In turn, the Ansible Automation Platform execution step authenticates against the correct controller instance without duplicating the workflow for each environment.

Organize credentials by environment

Credentials in automation orchestrator do not have a built-in environment label. To keep multi-environment workflows manageable:

  • Use a clear naming convention for credentials, such as aap-dev, aap-staging, aap-prod.
  • Scope credentials to a project when they should only be available to specific workflows.