# Guide for running PMM containers in AWS ECS **URL:** \ **Category:** PMM 1.x\ **Created:** [October 27, 2016, 8:11am UTC](https://forums.percona.com/t/guide-for-running-pmm-containers-in-aws-ecs/5176 "2016-10-27T08:11:51Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![weber](https://avatars.discourse-cdn.com/v4/letter/w/da6949/32.png) [@weber](https://forums.percona.com/u/weber)\ **Post date:** [October 27, 2016, 8:45am UTC](https://forums.percona.com/t/guide-for-running-pmm-containers-in-aws-ecs/5176/2 "2016-10-27T08:45:05Z")
It is okay when some subprocesses respawn, they have to finish finally with the expected exit code. The reason some processes depend on mysql which sometimes starts later but it’s not a problem at all. I have tried running PMM Server on Amazon ECS myself, I got success running “pmm-server” container. However, it was not clear to me what to do with the data volumes. Looks like “pmm-data” container is something not suitable for ECS, as all containers there should be disposable there (one off tasks). So I assume you have to manage volumes manually. Then it’s a question how to create them w/o being initialized first on the pmm-server image. It seems to me it’s easier to install docker on EC2 and spin up containers yourself. You probably don’t need to scale “pmm-server” in the way ECS designed for (web/app front/end backends). --- _[View the full topic](https://forums.percona.com/t/guide-for-running-pmm-containers-in-aws-ecs/5176)._