# Best practice in EC2 project tree

**URL:** <https://forum.ansible.com/t/best-practice-in-ec2-project-tree/17960>\
**Category:** Ansible Project\
**Created:** [April 12, 2015, 9:17am UTC](https://forum.ansible.com/t/best-practice-in-ec2-project-tree/17960 "2015-04-12T09:17:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tzach\_Livyatan1](https://avatars.discourse-cdn.com/v4/letter/t/9fc29f/32.png) [@Tzach\_Livyatan1](https://forum.ansible.com/u/Tzach_Livyatan1)\
**Post date:** [April 12, 2015, 9:17am UTC](https://forum.ansible.com/t/best-practice-in-ec2-project-tree/17960/1 "2015-04-12T09:17:53Z")

</div>

I have a project which includes setting up 5 different servers on EC2, each with 2-3 roles.  
So far, I created 3 file for each server:

- X-provisioning, which create the EC2 instance using module: ec2

- X-prepare, which apply the relevant roles for the server

- X-setup, which includes the two types above

With more servers type, the project root dir is becoming crowded.

Is there a way to move the above files to a (new?) role?  
In particular should, the X-provisioning be in a role?  
What is a good practice for such project structure?

Thanks  
Tzach