Subscribe
Sign in
AWS Guide for Startup Founders — Do’s & don’ts for first-time founders building on AWS
If you have $100k free credits but don't know your EC2s from your VPCs, this guide is for you. We'll steer you away from the most common AWS mistakes & help you make better infrastructure decisions.
Which services to use? How to not waste your credits?..
Which services to use? How to not waste your credits?..
8
Replies
Over the last year we’ve helped dozens of founders in our free AWS Office Hours. In the process, we’ve built up a very clear picture of what works for founders and what doesn’t.
AWS Documentation is plentiful but hard to navigate. More importantly, it doesn't help you make an informed decision. But founders don't have time - what's needed is guidance. Do this. Don't do that.
So we made this guide - if you’re a founder, this is a list of things you should and shouldn’t do with AWS.
Gotta disagree with the analysis of ElasticBeanstalk. Sure, it has some issues, but those seem to be amplified by most. It's definitely not the best option for "mission-critical" apps but let's be real, how many of us are building mission-critical applications?
Is the convenience offered by ElasticBeanstalk (can also use Procfiles now) not worth the rare downtime that can be resolved easily (I haven't faced a single issue in over a year btw) instead of paying hundreds of dollars on top of what you're already getting?
I still get overwhelmed every time I open the AWS console but I've learned a lot working with Igor and Mo. I think this guide will be useful to any founder who isn't an AWS expert.
Thundra Sidekick