# Sizing question in AWS

**URL:** <https://meta.discourse.org/t/sizing-question-in-aws/217671>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [February 9, 2022, 3:10pm UTC](https://meta.discourse.org/t/sizing-question-in-aws/217671 "2022-02-09T15:10:43Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)\
**Post date:** [February 9, 2022, 6:46pm UTC](https://meta.discourse.org/t/sizing-question-in-aws/217671/4 "2022-02-09T18:46:41Z")

</div>

> [@noginaze](#):
>
> Does anyone have some feedbacks on the worker nodes sizing, postgres instance type & redis instance type ?

This strongly depends on your traffic load, but since these are all fairly easy to change, I’d recommend you pick a size and see how well it performs. Aiming for between 3-10 app nodes to handle normal traffic is probably a good plan.

> [@Canapin](#):
>
> why not rely on the official way to install Discourse

As long as the deployed images are built with our launcher script, this would be a supported configuration. This would correspond to our `web_only` sample config which they’ve already said they’re using.

We wouldn’t be able to help with the Kubernetes side of things though.

---

_[View the full topic](https://meta.discourse.org/t/sizing-question-in-aws/217671)._