How to avoid Huge AWS Bills with AWS Budgets

[@pugazhenthimanoharan327]

Thanks Ryan. I was confused whether setting up budget action is actually mandatory even to receive alert notification. Now I know its not.

[@RyanHLewis]

Happy I could help!

[@dreamcatcherua]

Thank you, Ryan!

[@RyanHLewis]

You're welcome!

[@krzysztofzabolotny4802]

Amazin content. Thank you

[@RyanHLewis]

Glad you enjoyed it!

[@mikiallen7733]

thanks Ryan for the helpful input , but what If I use various different , DaaS , PaaS , SaaS , FaaS ..etc , then how do I budget for those individually and then holistically within AWS ? secondly is there a tool / documentation within AWS knowledge base which help me estimate costs accurately in case of consuming(e.g. storage say versus compute v.s. streaming v.s. say as the final app grows and more requests are being generated on the app by the final user ) of course types of data might play a role , but in my case I want to be able to use different types i.e. structured and unstructured ? your input is highly appreciated

[@RyanHLewis]

Thanks for the comment! I think the tool is pretty limited, actually, only for AWS. The AWS calculator might help you for estimating, though: calculator.aws

[@mfmn6397]

Great content! Would like you to share also what kind of data model that one should look and go for when choosing to push their system/website into these AWS services like EC2?

[@RyanHLewis]

Hi, thanks! Do you mean deployment model? Or are you thinking about database type stuff?

[@mfmn6397]

@@RyanHLewis Yes! Both actually. Since I've created & using EC2 services, even if it's a "free tier" plan, still, every month, I've to pay some amount of 💰 with less to no viewers or visitors at all. I'm worried, if the current data model that I used, will caused me someday (thinking of actually serve the production state of my website), have to pay a big chunk of money for something that I could potentially & possibly avoid doing/implementing them in the first place. For example, a youtube video from Fireship sharing about how a bad data model could caused & racked up your AWS bills. (are these the only infos that I should be mind of? Or there could be many more?) So, what would you suggest me to read and research on to make sure that this could be avoided? Right now, I'm making sure that some of the CRUD actions, if it's possible, I would try to make less interaction with the database. As the x amount of travel/read counts could cost me a lot of cash to spent on AWS bills later on (correct me if I'm wrong). Use of Redis, helps me a lot. But I don't know whether if this, is the right way of doing it. I'm sure that there would be more possible ways of achieving close to perfect implementation of correct data model. I just don't know where to start researching about this. If someone could point me to a or more possible directions I could go for, that would be great and much appreciated!

[@RyanHLewis]

@@mfmn6397 Got it. Thanks for the additional information! I think the best place to read further is with the Cost Optimization Pillar of the AWS Well-Architected Framework. AWS has produced a White Paper that helps explain how to manage cost effectively while getting the most performance possible. I think this should help you understand a few of the different ways that your infrastructure (data model) choices can impact your cost. Here's the link: docs.aws.amazon.com/wellarchitected/latest/framework/cost-optimization.html There's a link there for the white paper as well, which is good reading. I hope this helps!

[@mfmn6397]

@@RyanHLewis thanks! Appreciated it very much!