# Stateless Discourse Using AWS RDS/S3

**URL:** <https://meta.discourse.org/t/stateless-discourse-using-aws-rds-s3/216856>\
**Category:** Self-hosting\
**Created:** [February 2, 2022, 3:22pm UTC](https://meta.discourse.org/t/stateless-discourse-using-aws-rds-s3/216856 "2022-02-02T15:22:24Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![phil22](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/phil22/32/248480_2.png) [@phil22](https://meta.discourse.org/u/phil22)\
**Post date:** [February 2, 2022, 11:56pm UTC](https://meta.discourse.org/t/stateless-discourse-using-aws-rds-s3/216856/4 "2022-02-02T23:56:22Z")

</div>

Thanks very much both @pfaffman and @Poster_Nutbag - super useful!

EBS does sound like a better option - means we’d avoid diverging from [discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md).

Following from your advice I think I’m going to go for RDS but to pin to a specific commit of the discourse\_docker repo. Whilst it sounds like that will make upgrades more complex, I’m hoping it means that if we do have a problem with the server we’ll have everything safe on RDS and fairly swiftly be able to the same working state without a manual restore.

(We could achieve the same thing with EBS I think, but with volume encryption and unix magic to mount/dismount the volume between instances I’m a bit scared of the process of automating that)

---

_[View the full topic](https://meta.discourse.org/t/stateless-discourse-using-aws-rds-s3/216856)._