# Has anyone experience with AWS EC2 Container Service?
**URL:** https://meta.discourse.org/t/has-anyone-experience-with-aws-ec2-container-service/33432
**Category:** Self-hosting
**Tags:** hosting
**Created:** [2015年九月18日 09:12 UTC](https://meta.discourse.org/t/has-anyone-experience-with-aws-ec2-container-service/33432 "2015-09-18T09:12:50Z")
**Posts on this page:** 14
**Page:** 1
### Author:  [@terraboss](https://meta.discourse.org/u/terraboss)
#### Post date: [2015年九月18日 09:12 UTC](https://meta.discourse.org/t/has-anyone-experience-with-aws-ec2-container-service/33432/1 "2015-09-18T09:12:50Z")
Is anyone running Discourse on AWS’s new EC2 Container Service? Is it recommendable? Are there any known issues with managing them?
Thanks
https://www.youtube.com/embed/zBqjh61QcB4?feature=oembed&wmode=opaque
And a little bit longer… ;oP
[ ](https://www.youtube.com/watch?v=c0EnHl3o-L4)
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [2015年九月18日 21:10 UTC](https://meta.discourse.org/t/has-anyone-experience-with-aws-ec2-container-service/33432/2 "2015-09-18T21:10:24Z")
It doesn’t work, because of a couple reasons:
- (principally) the bootstrapping process, where all your configuration is applied & the database seeded, involves running code in the container, stopping the container, then starting it again with a different pid1
- backups are broken because the pg\_dump binary is mismatched with the server
- several other odd differences break other stuff, too (can’t remember right now)
---
### Author:  [@uwe\_keim](https://meta.discourse.org/u/uwe_keim)
#### Post date: [2017年十一月3日 14:55 UTC](https://meta.discourse.org/t/has-anyone-experience-with-aws-ec2-container-service/33432/3 "2017-11-03T14:55:54Z")
Any update/improvement on this, two years later?
Or will this never ever work at all with EC2 Container Services?
---
### Author:  [@rootsh3ll](https://meta.discourse.org/u/rootsh3ll)
#### Post date: [2017年十一月3日 15:03 UTC](https://meta.discourse.org/t/has-anyone-experience-with-aws-ec2-container-service/33432/4 "2017-11-03T15:03:27Z")
not sure about container service but I am running discourse under docker along with a side on wordpress(non-dockerised) and not facing issues managing them. as it is being reverse-proxied by nginx to the discourse container.
so everything is organised.
---
### Author:  [@schungx](https://meta.discourse.org/u/schungx)
#### Post date: [2017年十一月3日 19:54 UTC](https://meta.discourse.org/t/has-anyone-experience-with-aws-ec2-container-service/33432/5 "2017-11-03T19:54:33Z")
A container service manages docker and the base OS for you AFAIK. You don’t have root access. You just throw a container in and the service runs it.
Discourse requires root access to config.
---
### Author:  [@rootsh3ll](https://meta.discourse.org/u/rootsh3ll)
#### Post date: [2017年十一月3日 20:03 UTC](https://meta.discourse.org/t/has-anyone-experience-with-aws-ec2-container-service/33432/6 "2017-11-03T20:03:05Z")
but on EC2 you do have root access.
As OP said discourse doesn’t work on ECS. I wonder why? even when you have root access.
AFAIK, ECS is simply EC2 running docker for you. so, I wonder why it cannot run discourse on ECS. whilst I am running discourse on EC2.
PS: don’t mind If I am wrong. I don’t know much about ECS
---
### Author:  [@schungx](https://meta.discourse.org/u/schungx)
#### Post date: [2017年十一月3日 21:25 UTC](https://meta.discourse.org/t/has-anyone-experience-with-aws-ec2-container-service/33432/7 "2017-11-03T21:25:30Z")
ECS takes away the OS and decker management from you. For example they manage all the upgrades and patches. You dont have to do those. So it is not a complete VM. It is a managed service. You only provide a container.
---
### Author:  [@rootsh3ll](https://meta.discourse.org/u/rootsh3ll)
#### Post date: [2017年十一月3日 21:38 UTC](https://meta.discourse.org/t/has-anyone-experience-with-aws-ec2-container-service/33432/8 "2017-11-03T21:38:21Z")
This way it’s impossible to run discourse on ECS. since discourse needs to be _root_
---
### Author:  [@terraboss](https://meta.discourse.org/u/terraboss)
#### Post date: [2017年十一月3日 21:50 UTC](https://meta.discourse.org/t/has-anyone-experience-with-aws-ec2-container-service/33432/9 "2017-11-03T21:50:59Z")
> [@rootsh3ll](#):
>
> since discourse needs to be root
Can you explain why? Is there any post at meta that’s linked on this topic?
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2017年十一月3日 21:56 UTC](https://meta.discourse.org/t/has-anyone-experience-with-aws-ec2-container-service/33432/10 "2017-11-03T21:56:45Z")
It will work fine on Ecs , bootstrap an image push to registry and then specify env and volumes
---
### Author:  [@rootsh3ll](https://meta.discourse.org/u/rootsh3ll)
#### Post date: [2017年十一月3日 22:00 UTC](https://meta.discourse.org/t/has-anyone-experience-with-aws-ec2-container-service/33432/11 "2017-11-03T22:00:15Z")
as sam confirms above, it should work on ecs.
---
### Author:  [@schungx](https://meta.discourse.org/u/schungx)
#### Post date: [2017年十一月3日 22:00 UTC](https://meta.discourse.org/t/has-anyone-experience-with-aws-ec2-container-service/33432/12 "2017-11-03T22:00:38Z")
That’s right. I suppose the container must be prebuilt outside for the exact config then thrown into ECS.
---
### Author:  [@rootsh3ll](https://meta.discourse.org/u/rootsh3ll)
#### Post date: [2017年十一月3日 22:01 UTC](https://meta.discourse.org/t/has-anyone-experience-with-aws-ec2-container-service/33432/13 "2017-11-03T22:01:33Z")
will try that and possibly write a thorough article for more people to come 🙂 Thanks sam
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2017年十一月3日 22:02 UTC](https://meta.discourse.org/t/has-anyone-experience-with-aws-ec2-container-service/33432/14 "2017-11-03T22:02:06Z")
A lot of config can be provided via env on a bootstrapped image, majority of it