# Has anyone successfully gotten Discourse running in AWS ECS / similar?

**URL:** <https://meta.discourse.org/t/has-anyone-successfully-gotten-discourse-running-in-aws-ecs-similar/141694>\
**Category:** Development\
**Created:** [February 15, 2020, 5:54pm UTC](https://meta.discourse.org/t/has-anyone-successfully-gotten-discourse-running-in-aws-ecs-similar/141694 "2020-02-15T17:54:38Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![lktmxjv](https://avatars.discourse-cdn.com/v4/letter/l/fbc32d/32.png) [@lktmxjv](https://meta.discourse.org/u/lktmxjv)\
**Post date:** [February 15, 2020, 5:54pm UTC](https://meta.discourse.org/t/has-anyone-successfully-gotten-discourse-running-in-aws-ecs-similar/141694/1 "2020-02-15T17:54:38Z")

</div>

I’ve read threads like [this](https://meta.discourse.org/t/can-discourse-ship-frequent-docker-images-that-do-not-need-to-be-bootstrapped/33205) and others, and it seems like to date, there’s no easy way to pop a Discourse image into something like ECS, or GKE or whatever container orchestration you like and have it work easily…

I use Terraform to manage an Elasticache cluster, an RDS instance, and an ECS cluster. I just want to be able to say, “Here’s my Discourse image, and here are the environment variables to connect to Postgres, Redis, SMTP, etc.”

Does anything like this exist in 2020? It seems like in all the conversations around this topic previously, no satisfying resolution was reached, and we’re still stuck with Discourse’s custom scripts that defy container conventions and break compatibility with the idiomatic way people use containers…

---

_[View the full topic](https://meta.discourse.org/t/has-anyone-successfully-gotten-discourse-running-in-aws-ecs-similar/141694)._
