I am about to use some AWS services for the first time and I am a bit worried about the disasters that happen because of the pay-for-what-you-use business modal, a simple loop can cause you a 5 figure bill.<p>So I am asking about the necessary things I should know as a beginner AWS user to avoid such problems.<p>Also, any other info/advice to reduce costs is welcome.<p>The services I will be using are S3, Elemental MediaConvert, and CloudFront.<p>For video streaming.
To mention just the first few that come to mind:<p>- Setup aws billing cost alerts based on thresholds<p>- Consult AWS billing dashboard daily first, then weekly, then monthly. There is a "forecast" that can tell where you're going to land at the end of the month (ballpark).<p>- Understand how s3 charges, take advantage of the various storage classes. Setup s3 bucket lifecycle to delete objects if you have expiring objects.<p>- Make sure you setup backups. This can be a source-code repo or something like glacier. Make sure you understand how it works. tl;dr archiving is cheap, retrieving is expensive & slow.<p>- Make sure you understand how data transfer is charged on AWS (e.g. <a href="https://aws.amazon.com/blogs/architecture/overview-of-data-transfer-costs-for-common-architectures/" rel="nofollow noreferrer">https://aws.amazon.com/blogs/architecture/overview-of-data-t...</a> - there are many others)<p>- Avoid services that use the AWS API to fetch metrics unless you have bandwidth to monitor closely. I've seen companies getting charged 6-7k/month for months, without anyone noticing, just because a prom exporter was abusing the API. When I took notice, three months in, I removed the exporter without letting anyone know. Scream-test was passed in flying colours, no one complained :-)<p>Good luck! :D
Just curious... are you using it for a personal project or is it part of a requirement for a role/employment?<p>I've seen this happen: <a href="https://www.reddit.com/r/ProgrammerHumor/comments/w4eo12/using_aws/" rel="nofollow noreferrer">https://www.reddit.com/r/ProgrammerHumor/comments/w4eo12/usi...</a><p>I don't have any great pointers unfortunately, though I met someone not too long ago who has a product to help with monitoring AWS costs: <a href="https://www.cloudforecast.io/" rel="nofollow noreferrer">https://www.cloudforecast.io/</a><p>Disclaimer: I've never used this tool as I don't use AWS but if I did have to use AWS, I would likely try something like this at least early in the game to avoid getting rekd.
In my view this makes it very difficult to use AWS or Azure for fun or as part of a small operation. It's fine when you have a big organization monitoring this stuff and a support team, but how will you feel if you get a billing alert at 3am when you're asleep or out at a nightclub telling you there is a massive overspend. Are you going to put yourself on 24hr support?<p>I'm just moving from somewhere with AWS and a large team supporting it onto Azure with a much smaller team where I'll have full access to creating any component and the billing information, will be interesting to see what happens. Even then though it's not really publicly accessible so we shouldn't get anything too unexpected.
AWS has tools to set spending thresholds and to alert when you go over. Set those up first thing. Regularly (daily) check your usage in the dashboard and stop things before they get out of hand.<p>You will eventually accidentally spend more than you want to. This is a feature. Just try to catch it early and course correct before annoying becomes disaster.