# AWX question from a beginner :-(

**URL:** <https://forum.ansible.com/t/awx-question-from-a-beginner/38144>\
**Category:** Ansible Project\
**Tags:** awx\
**Created:** [June 22, 2023, 3:14pm UTC](https://forum.ansible.com/t/awx-question-from-a-beginner/38144 "2023-06-22T15:14:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Federico\_Rovelli](https://avatars.discourse-cdn.com/v4/letter/f/e79b87/32.png) [@Federico\_Rovelli](https://forum.ansible.com/u/Federico_Rovelli)\
**Post date:** [June 22, 2023, 3:14pm UTC](https://forum.ansible.com/t/awx-question-from-a-beginner/38144/1 "2023-06-22T15:14:38Z")

</div>

I have an Ansible environment already configured (control server and managed servers) and I want to manage it with AWX.  
I have installed AWX and start a GUI but I don’t know in what way I can connect AWX to my configuration manually done.

---

<div class="post-metadata">

**Author:** ![Evan\_Hisey](https://avatars.discourse-cdn.com/v4/letter/e/ce73a5/32.png) [@Evan\_Hisey](https://forum.ansible.com/u/Evan_Hisey)\
**Post date:** [June 22, 2023, 3:41pm UTC](https://forum.ansible.com/t/awx-question-from-a-beginner/38144/2 "2023-06-22T15:41:54Z")

</div>

AWX/Ansible Tower is designed to work with a Git repo or other Source Control holding each “project” via URI. In general this is also the simplest way to handle things. There is an option to use “manual” loaded projects but requires hand loading the playbooks into the tower container. To do this you have to manually copy the playbooks to the AWX container something like this:

- Create a directory in /var/lib/awx/projects directory on the local ansible AWX container. Example, /var/lib/awx/projects/project1
- Place the playbook in ‘project1’ directory. Example, var/lib/awx/projects/project1/example\_playbook.yml (follow process as described [here](https://docs.ansible.com/ansible-tower/latest/html/userguide/projects.html#manage-playbooks-manually))
- Create a manual project in Tower (follow process as described [here](https://docs.ansible.com/ansible-tower/latest/html/userguide/projects.html#add-a-new-project))
- Use that project in job template to see the playbook ‘example\_playbook.yml’

---

<div class="post-metadata">

**Author:** ![Federico\_Rovelli](https://avatars.discourse-cdn.com/v4/letter/f/e79b87/32.png) [@Federico\_Rovelli](https://forum.ansible.com/u/Federico_Rovelli)\
**Post date:** [June 22, 2023, 3:58pm UTC](https://forum.ansible.com/t/awx-question-from-a-beginner/38144/3 "2023-06-22T15:58:09Z")

</div>

Thanks Evan for the answer, but I have already configured my Ansible environment manually under /etc/ansible outside container.  
Now, after one year I decided to install AWX and I tought was possible to manage my configuration with AWX.

What you sugget is replicate manually on AWX the same things I already done on the server ☹

Regards  
Ciao

---

<div class="post-metadata">

**Author:** ![Evan\_Hisey](https://avatars.discourse-cdn.com/v4/letter/e/ce73a5/32.png) [@Evan\_Hisey](https://forum.ansible.com/u/Evan_Hisey)\
**Post date:** [June 22, 2023, 7:51pm UTC](https://forum.ansible.com/t/awx-question-from-a-beginner/38144/4 "2023-06-22T19:51:09Z")

</div>

Correct. AWX was not intended managing a seperate environment. Honestly, unless you need schedules and callbacks, or shared operation management like in enterprise it is not very useful.

---

<div class="post-metadata">

**Author:** ![Nico\_Kadel-Garcia](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nico_kadel-garcia/32/9998_2.png) [@Nico\_Kadel-Garcia](https://forum.ansible.com/u/Nico_Kadel-Garcia)\
**Post date:** [June 25, 2023, 3:38pm UTC](https://forum.ansible.com/t/awx-question-from-a-beginner/38144/5 "2023-06-25T15:38:46Z")

</div>

AWX and Ansible Tower are really useful when the person or team doing  
structure and demanding policy compliance need to hand off specific,  
well defined tasks to "Jo-Jo the Monkey Boy", the untrained intern  
who's not yet and may never learn how things really work. Red Hat is  
now pushing "Event Driven Ansible", integrating ansible through  
Ansible Tower with status reporting and recovery operations, and for  
such large scale work, it can be \*really useful\* to say "this team can  
do these steps, these people can edit the tasks, these people can  
reset privileges for other people, etc."

For a small, consistent environment? As you've found, ansible-core by  
itself is enough.

Nico Kadel-Garcia
