2
1 Comment

AWS - what is cost-optimum config for indie startup like mine?

Hello Indie hackers,

I am about to launch a very thin REST API that powers my mobile app for books. Nothing fancy - just text + user db that stores email, and subscription data.

The cloud is AWS. I use lambda for REST. RDS (PostGreSQL) for DB. Cognito for user authentication.

My questions are pretty broad, but I do not find any general answers elsewhere. I am primarily worried about costs.

  • What is general configuration that one starts with in above things? For instance, I have an RDS instance - what type (t2 large etc etc) I should begin with to maximize my savings?

  • Any pointers to take care of reducing lambda costs? My some calls exceed 200ms and I do not know what should be the ideal numbers. I am still under FREE tier but I do not want to be bombed once pricing starts kicking in.

  • Any other factors I forgot to mention, but are super critical that affect my budget?

  • do you guys have any estimates of your monthly bills per user/requsts?

Thanks for all your time and thoughts on this....

on August 18, 2020
  1. 1

    Anyone, on AWS? I was also curious as to how we sparse out the deployment across regions i.e. EU, USA etc...do we open multiple AWS accounts since the default AZ is part of the URL?