Re:Manage AWS costs on non-production environments
by radedespodovski on Thursday May 14, 2020 @09:34AM
(#23179288)
Probably if you have a couple of accounts and infrastructure units then probably you could set up similar configuration which will do the job. We at Microtica also started with that approach but as we started to expand with AWS accounts and multiple infrastructure units it become hard to manage all of it.
Imagine if you have to use different tags as selectors with different schedule times for each. You would have to control each of them through CloudFormation or even manually log into EC2 instance to update the script.
In addition, the solution provides few more benefits: 1. Auto-tagging 2. Native integration with infrastructure provisioned with Microtica 3. Cost and Saving dashboard 4. You don't need to manage your own infrastructure which will handle start/stop operations for EC2 and RDS 5. Schedule notifications
Re:Manage AWS costs on non-production environments
by scarface74 on Thursday May 14, 2020 @10:15AM
(#23179789)
Why would I trust any company that is reckless enough to recommend giving their service full access to my account - with any access to my account?
This isn't as straightforward as it might be - it takes a blog-post to explain it: https://schen1628.wordpress.com/2014/02/04/auto-start-and-st... , https://www.thinkforwardmedia.com/automating-ec2-instances-a...
My own notes and a relevant AWS Lambda script, in Python: https://pinboard.in/u:MaxBarraclough/b:f0b059256f32 , https://gist.github.com/MaxBarraclough/211e569cb57b46c0ddb48...