# Workflow to deploy on AWS with some additional tools

**URL:** https://discourse.roots.io/t/workflow-to-deploy-on-aws-with-some-additional-tools/4554
**Category:** archived 🗄
**Created:** 2015-08-24T02:05:46Z
**Posts:** 2
**Showing post:** 2 of 2

## Post 2 by @fullyint — 2015-08-24T03:10:47Z

1. I think Trellis works out of the box on AWS if you just change to [`admin_user: ubuntu`](https://github.com/roots/trellis/blob/c9183c9aa3ef09507c4dfb7a9cc342f9d5d832d3/group_vars/all#L35) and follow the [README](https://github.com/roots/trellis).

2. I can’t comment on the other questions, but note you can enable [xdebug in the VM configs](https://github.com/roots/trellis/blob/c9183c9aa3ef09507c4dfb7a9cc342f9d5d832d3/group_vars/development#L50-L57) and [memcached](https://github.com/roots/trellis/blob/c9183c9aa3ef09507c4dfb7a9cc342f9d5d832d3/dev.yml#L21) is included [by default](https://github.com/roots/trellis/tree/c9183c9aa3ef09507c4dfb7a9cc342f9d5d832d3/roles/memcached).

> [@tannakartikey](#):
>
> I am moving from cowboy coding to such kind of develop environment for better.

Ah Yeah! :+1:

With so many customizations/integrations planned, I’d suggest starting by getting a vanilla trellis working, with all default settings (but change `admin_user`). Then start adding customizations one at a time, testing as you go. Might sound obvious, but the getting started process – and potential debugging – seems unnecessarily difficult sometimes when people start right in with a lot of customizations.

---

_[View the full topic](https://discourse.roots.io/t/workflow-to-deploy-on-aws-with-some-additional-tools/4554)._