# AWX vs AAP - Containerized Install, no ability to add instances

**URL:** <https://forum.ansible.com/t/awx-vs-aap-containerized-install-no-ability-to-add-instances/10019>\
**Category:** Project Discussions\
**Tags:** aap, awx\
**Created:** [October 8, 2024, 12:54pm UTC](https://forum.ansible.com/t/awx-vs-aap-containerized-install-no-ability-to-add-instances/10019 "2024-10-08T12:54:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kmf](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kmf/32/490_2.png) [@kmf](https://forum.ansible.com/u/kmf)\
**Post date:** [October 8, 2024, 12:54pm UTC](https://forum.ansible.com/t/awx-vs-aap-containerized-install-no-ability-to-add-instances/10019/1 "2024-10-08T12:54:56Z")

</div>

No ability to add Instances in the Containerized version of AAP.

 ![Screenshot from 2024-10-08 14-14-26](https://us1.discourse-cdn.com/ansible/original/2X/1/13ccca7c0021e2f946fce12f8b6bef1662d101af.png)  
 ![Screenshot from 2024-10-08 14-14-10](https://us1.discourse-cdn.com/ansible/original/2X/5/5a738dc96aac287b7f3249d06221979d2bb157a2.png)

 ![Screenshot from 2024-10-08 14-52-40](https://us1.discourse-cdn.com/ansible/original/2X/f/ffd2f428393cfa727f64dea5fb1a9ec8ca1f3655.png)

Docs show something,

 ![CleanShot 2024-10-08 at 10.43.23@2x](https://us1.discourse-cdn.com/ansible/original/2X/b/b726bfc1215ebf87fff043dcc2dbbf8aa22d0d98.jpeg)

What’s the story here? Seems you need OpenShift

---

<div class="post-metadata">

**Author:** ![Denney-tech](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/denney-tech/32/1556_2.png) [@Denney-tech](https://forum.ansible.com/u/Denney-tech)\
**Post date:** [October 9, 2024, 2:28pm UTC](https://forum.ansible.com/t/awx-vs-aap-containerized-install-no-ability-to-add-instances/10019/2 "2024-10-09T14:28:41Z")

</div>

I do not work for Red Hat, and this is a _community_ forum so please consult with your TAM or submit a support case for technical help with your AAP install.

With that prefaced, I believe you need to add your instances in your inventory file and rerun the installation playbook. See #3.2.4. Or review #1.5 in the containerized installation doc.

Edit: I thought this was in Get Help, but I see now that you were asking about _why this is different_. The answer is probably that these are technically different deployment methods in the AAP vs AWX examples, and that the preferred method of modifying the instances in the AAP scenario is through the installation method.

---

<div class="post-metadata">

**Author:** ![Phil\_Griffiths](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/phil_griffiths/32/2779_2.png) [@Phil\_Griffiths](https://forum.ansible.com/u/Phil_Griffiths)\
**Post date:** [October 10, 2024, 3:57pm UTC](https://forum.ansible.com/t/awx-vs-aap-containerized-install-no-ability-to-add-instances/10019/3 "2024-10-10T15:57:00Z")

</div>

Hi Karl.

I’m a Red Hat Ansible PM who can provide an answer.  
Caleb is right. For containerized, you add your new nodes into the installer inventory file and re-run the installation.

The ‘hot add’ type feature was added into the platform for those k8s-based supported deployments specifically so that customers could add an ingress into their on-premise datacenters from a cloud based AAP. This effectively provides a cloud based managed control plane but customer supplied execution plane.

No plans right now that I can tell you about that will change the above, but with AAP 2.5 we now do have a better centralized management point of entry where there is potential to do things more flexibility.

Regards  
Phil.