I was wondering if you had an estimation of the pricing when self hosting on AWS ? I have made a standard self hosting installation and I am quite surprise to see the pricing for : Elasticache (between 150 and 200$ per month) RDS (a bit more than 100$ per month). I was wondering if this is "standard" costs that you may have experienced ? Thank you.

Yep! That was my experience as well. You can check out this thread: https://discord.com/channels/905144809105260605/1322019051219976285/1323100126465622160 There are some small workarounds you can try to lower the cost, but IMHO all of these little workarounds made me a little uncomofrtable -- and I ended up breaking and then just going down-under into localhost for development for a while -- and then back to AWS (now) when I'm almost ready to launch.

Thanks for the answer. I'm quite surprise concerning the cache for example. I'm in a dev environnement with very little data, and when I check the elasticache it happens to take 3Go of Cache. Which seems huge.

Medplum's cache usage sets items to expire after 24 hours. Redis will naturally hold on to cached items until it's full and needs to evict. It's not that it "needed 3 GB" of cache, but rather that your Redis instance supported it, so Medplum used it. For a small deployment, you can definitely get away with ElastiCache cache.t2.micro or cache.t3.micro, which fit into AWS free tier, and would therefore cost $0. If you truly want to minimize costs, you can run everything on a single EC2 host. See: https://www.medplum.com/docs/self-hosting/install-on-ubuntu Medplum requires BullMQ for background job management, which is pretty integral to the system. BullMQ requires Redis, so it's essentially part of the stack today. It's conceivably possible to disable enough parts of the system to make BullMQ and Redis optional. We would happily accept pull requests if anyone wants to help out!

Hi @cody Thanks for all the information. I'm currently watching to do a self install on a simple EC2 for our development installation. I don't see anything about running bots on a simple EC2. Is it somehow possible ? Thanks for the answer and the time !

@thomabig , if you're not using AWS lambdas for bots , you can follow these docs to run bots as in-process threads https://www.medplum.com/docs/bots/running-bots-locally

Ok, awesome, so I could have a dev environnement which uses vmcontext bot in an EC2, and then a preproduction environnement with a small redis instance for testing purpose and finally a prod environnement with a standard instance on aws ! thanks for all the info !

That's right!