This week too, I haven't get the time to read paper 😭
I was working into AWS DevOps
specifically AWS Cost Optimization for servers
You have an EC2 instance (some server) sitting completely idle, doing absolutely nothing. You want to kill it, but you can’t because you don't want to lose your setup configuration like the docker and other packages installed, and you definitely don't want your public IP address to change too.
If you just leave it running, Jeff Bezos wins 😂, and your money burns alive. So, what are the cost optimizations?
The simplest trick is just stopping the instance when you aren't using it (like weekends or overnight) and starting it back up when you do. Useful for dev or test servers.
You commit to a specific instance type (like a t3.micro) for a 1 or 3-year term. AWS rewards your commitment with at least a 30% discount!
The catch: It’s rigid.
If Reserved Instances feel too restricting, Savings Plans are the cooler, more flexible. Instead of committing to a specific machine, you commit to spending a specific amount of money per hour (e.g., $1/hour). The best part? It automatically applies discounts across EC2, AWS Lambda, and ECS Fargate dynamically.
Want massive discounts up to 60% (or more) off the original price? Use Spot Instances. This is AWS selling their unused spare capacity for dirt cheap.
The catch: If someone else offers to pay full price, AWS will kick you off the server with a 2-minute warning. Great for stateless apps like background running task, but not for database hell no
#devops@qalabit
I was working into AWS DevOps
specifically AWS Cost Optimization for servers
You have an EC2 instance (some server) sitting completely idle, doing absolutely nothing. You want to kill it, but you can’t because you don't want to lose your setup configuration like the docker and other packages installed, and you definitely don't want your public IP address to change too.
If you just leave it running, Jeff Bezos wins 😂, and your money burns alive. So, what are the cost optimizations?
1. Obviously Stop & Start
The simplest trick is just stopping the instance when you aren't using it (like weekends or overnight) and starting it back up when you do. Useful for dev or test servers.
2. Prepaid Packages (Reserved Instances)
You commit to a specific instance type (like a t3.micro) for a 1 or 3-year term. AWS rewards your commitment with at least a 30% discount!
The catch: It’s rigid.
3. Savings Plans
If Reserved Instances feel too restricting, Savings Plans are the cooler, more flexible. Instead of committing to a specific machine, you commit to spending a specific amount of money per hour (e.g., $1/hour). The best part? It automatically applies discounts across EC2, AWS Lambda, and ECS Fargate dynamically.
4. Spot Instances
Want massive discounts up to 60% (or more) off the original price? Use Spot Instances. This is AWS selling their unused spare capacity for dirt cheap.
The catch: If someone else offers to pay full price, AWS will kick you off the server with a 2-minute warning. Great for stateless apps like background running task, but not for database hell no
#devops@qalabit