# Building Execution Environments in AAP 2.7 without the command line

**URL:** <https://forum.ansible.com/t/building-execution-environments-in-aap-2-7-without-the-command-line/45903>\
**Category:** Guides, FAQs & Howtos\
**Tags:** aap, howto, ee\
**Created:** [June 10, 2026, 6:32pm UTC](https://forum.ansible.com/t/building-execution-environments-in-aap-2-7-without-the-command-line/45903 "2026-06-10T18:32:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![IPvSean](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ipvsean/32/1153_2.png) [@IPvSean](https://forum.ansible.com/u/IPvSean)\
**Post date:** [June 10, 2026, 6:32pm UTC](https://forum.ansible.com/t/building-execution-environments-in-aap-2-7-without-the-command-line/45903/1 "2026-06-10T18:32:01Z")

</div>

One of my teammates, Aubrey, recently put together a walkthrough of the new **Execution Environment Builder** in Ansible Automation Platform 2.7, and I thought it was worth sharing here for anyone who spends time maintaining execution environments.

The demo shows how to build and publish an execution environment directly from the Automation Portal UI. Instead of manually creating definition files and running build commands, you can select collections, add Python/system dependencies, and let AAP handle the build and publishing process.

A few things covered in the video:

- Selecting a base execution environment image
- Adding collections from Private Automation Hub, GitHub, or GitLab
- Including Python and system package dependencies
- Publishing the resulting image to a container registry
- Tracking build progress and logs from the UI

What I found interesting is that it lowers the barrier for teams that may not be comfortable maintaining container build workflows but still need custom execution environments for things like network automation, cloud automation, or integrating additional Python libraries.

If you’ve been curious about how the new builder works in practice, this gives a good end-to-end look at the workflow.

[![](https://us1.discourse-cdn.com/ansible/original/2X/8/81ad9bc88e7d2a928ffe4b056d82f762604a7a47.jpeg "Build an Execution Environment with the Automation Portal") ](https://www.youtube.com/watch?v=wV0tUZTGbQM)

I’m also curious how others are currently managing their execution environments today—manually with `ansible-builder`, through CI/CD pipelines, or something else?

---

<div class="post-metadata">

**Author:** ![johan](https://avatars.discourse-cdn.com/v4/letter/j/dec6dc/32.png) [@johan](https://forum.ansible.com/u/johan)\
**Post date:** [June 10, 2026, 7:15pm UTC](https://forum.ansible.com/t/building-execution-environments-in-aap-2-7-without-the-command-line/45903/2 "2026-06-10T19:15:50Z")

</div>

hello, ansible-builder CLI user here,

is Automation portal only for AAP 2.7 OCP or does it work for containerized installations too ?

It looks great for most use cases, but I fear edge cases : when you need a python module which requires compilation, or when pip tries to uninstall from base image some RPM installed python module to install a more recent version, or when you need to include third-party binaries (kubectl, oc, …).

I already had a request for an old ansible collection I had to package first as a tar.gz, or for a collection which during its install process tried to download some components from [github.com](http://github.com) (not always accessible when you are behind corporate firewalls).

Working with different base images (ubi 8 or ubi 9) can be annoying too, as you have to switch to the approprate base rpms / appstream / codeready / EPEL repo.

Eventually, I realize i only have a few “simple” cases ☹

---

<div class="post-metadata">

**Author:** ![nicholcd](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nicholcd/32/3488_2.png) [@nicholcd](https://forum.ansible.com/u/nicholcd)\
**Post date:** [June 11, 2026, 7:51am UTC](https://forum.ansible.com/t/building-execution-environments-in-aap-2-7-without-the-command-line/45903/3 "2026-06-11T07:51:03Z")

</div>

I have the AAP 2.7 Containerized deployment and I find no Execution Environment Builder, this must only be for the OpenShift deployment.

---

<div class="post-metadata">

**Author:** ![IPvSean](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ipvsean/32/1153_2.png) [@IPvSean](https://forum.ansible.com/u/IPvSean)\
**Post date:** [June 11, 2026, 1:19pm UTC](https://forum.ansible.com/t/building-execution-environments-in-aap-2-7-without-the-command-line/45903/4 "2026-06-11T13:19:23Z")

</div>

Hey @nicholcd ,

Sorry it is a little bit confusing. There is a separate installation for automation portal. It is included as part of the Red Hat subscription, but it is a separate instance, with its own webUI. Here is the documentation: [https://docs.redhat.com/en/documentation/red\_hat\_ansible\_automation\_platform/2.7/install-con\_self\_service\_rhel\_appliances](https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-con_self_service_rhel_appliances)
