👑 "All we have to decide is what to do with the time that is given us." - J. R. R. Tolkien
This week, I share tips to cut AWS costs while sprucing up my blog and reflecting on GCP's downtime.
Hello friends!
I hope your week was good. I spent decent amount of time cleaning up my house for the upcoming festive season, some coding and a bit of writing. I also revamped parts of my blog to make it look better.
Was this forwarded to you? You can subscribe here!
📰 News of the week
A major power failure hit Google cloud, europe-west-3(Germany) region, causing a downtime that lasted 12 hours and 39 minutes on 24th Oct, last week. Read the incident report here.
For next 365 days, even if they encounter zero downtimes, GCP’s uptime will still be capped at 99.856%. Whatever happened to five nines! 🤪
🎉 Let’s begin!
There are a million ways to reduce your AWS bills. While financial instruments like savings plan come in very handy when you begin your cost optimisation journey, it is equally important to try and improve overall health of your infrastructure and application to reduce costs more organically.
I wrote about some ways in which you can do so. Here’s a brief summary.
Delete unused resources: One deleted resource means one less thing to worry about when planning other cost optimisation activities.
Right sizing: Monitoring usage and migrating to cheaper instances where ever possible.
Spot instances: Cheapest (up to 90% cheaper than on demand instances), most flexible, but slightly inconvenient way to reduce your AWS bills.
Auto scaling: Leverage the elasticity of cloud to reduce your usage during off hours.
Application performance: Optimising code, caching, adding DB indices, rate limiting, optimise UX to avoid unnecessary calls and so on to reduce CPU and memory footprint.
Read the full article here and hit reply to share what you think.
If you really want to go deep into how AWS’ savings plan work and how you should buy them, go ahead and read my handbook on it. It is completely free.
Around the web on AWS cost optimisation
Official AWS
Amazon Managed Service for Apache Flink now supports per second billing
AWS Billing Conductor now supports RI and Savings Plans coverage and utilization reports
Joke
Why did Amazon brought back RTO?
Because they couldn't afford so many employees using Chime for free. 😜
That's all for now, folks! Have a great week. Keep reading and learning.
Shubham