aramalipoor / aws-cost-saver Goto Github PK
View Code? Open in Web Editor NEWA tiny CLI tool to help save costs in development environments when you're asleep and don't need them!
License: MIT License
A tiny CLI tool to help save costs in development environments when you're asleep and don't need them!
License: MIT License
Suggested by weeefun on HN
Suggested by adamlklein on HN
I use AWS Elasticache for Redis and also can shut that down or stop it to save some costs, really thanks for this project, looking for something like it for a while now!
This will enable using aws-cost-saver in a Lambda potentially.
Discussed by rxDotIo and twratl on reddit.
aurora-PostgreSQL DB instances are not eligible for stopping and starting.
.
Suggested by weeefun on HN
Version - [email protected]
Service/Trick - stop-fargate-ecs-services
I have around 23 ECS tasks running. The current latest version is throwing this error though the stop-fargate-ecs-services is successful and in AWS I could see all tasks desired count is set to 0.
I guess this is because of some timeout settings.
Error -
✔ partially finished, with 1 failed tricks out of 3.
◎ conserve: stop-fargate-ecs-services
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
✔ service/*******
✔ desired count
set desired count to zero
↓ auto scaling
↓ no scalable targets defined
************************
✔ partially finished, with 1 failed tricks out of 3.
Error: ConservePartialFailure
When using --state-file s3:// on a daily scheduled cron., the job fails for the second time and further with error
→ State file already exists: s3://***/staging-state-file.json ? Are you sure you want to OVERWRITE existing state-file? You will not be able to restore to previously conserved resources! (y/N)
Please enable overwrite flag while using --state-file s3://
Hello,
I'd like to suggest adding support for environment variables for profile, access key id, secret access key, default region, etc. replicating what the AWS cli and SDK's support.
I'm happy to contribute as well but wanted to see your interest first. :-)
Autoscaling groups kick in once you shut down the EC2 instances. To prevent this you must suspend them.
It would be great if you could include them in your process.
Here are the scripts I use pre conserve and restore
aws autoscaling describe-auto-scaling-groups --output=yaml | grep AutoScalingGroupName | awk '{print $2}' | xargs -n1 aws autoscaling suspend-processes --auto-scaling-group-name
aws autoscaling describe-auto-scaling-groups --output=yaml | grep AutoScalingGroupName | awk '{print $2}' | xargs -n1 aws autoscaling resume-processes --auto-scaling-group-name
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.