Execution Environments Demystified: Build Once, Run Anywhere, Pin Every Version
Adding and Managing EEs in AWX
To add an execution environment to your AWX instance, go to Execution Environments in the left-hand menu and click on the Add button. You'll need to provide the name, description, pull policy, organization, container image, and the credentials required to access the image.
In the image field, enter the URL of the container image you want to use. This image should be built using Ansible Builder and include all the necessary dependencies for your automation tasks. Ensure the image is accessible to the AWX instance, which may require providing credentials to pull it from a private registry.
The pull policy has three options equivalent to the following Docker pull policies:
- Always: Always pull the image, even if it is already present.
- If Not Present: Pull the image only if it is not already present.
- Never: Never pull the image, even if it is not present.
If you prefer not to restrict the execution environment to a single organization, you can leave the organization field empty. This makes the execution environment available to every organization in your AWX instance.
For instance, if you have quay.io/ansible/awx-ee:24.4.0 as the container image for your execution environment and you want to use the tag 24.5.0 as an additional execution environment, you should use the image URL quay.io/ansible/awx-ee:24.5.0 and provide the necessary credentials to pull the image. Here are the steps:
- Use
AWX EE (24.4.0)in the Name field. - Use
quay.io/ansible/awx-ee:24.5.0in the Image field. - Since Quay.io is a public registry, you don't need to provide any credentials to pull the image.
AWX in Action
Ansible Orchestration at ScaleEnroll now to unlock all content and receive all future updates for free.
