New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

take local remediation options (cloudwatchd babysitter) #4

Open

rremer opened this issue Jan 30, 2013 · 0 comments

Assignees

Labels

Milestone

Owner

rremer commented Jan 30, 2013

Cloudwatch Actions (http://aws.amazon.com/about-aws/whats-new/2013/01/08/use-amazon-cloudwatch-to-detect-and-shut-down-unused-amazon-ec2-instances/?ref_=pe_8050_27877550) are handy, but for quick local remediation it would be faster to have cloudwatchd be the first responder. Permissions will need to be honored like cron.d with invocation user, building an incrimental backoff into INTERVAL that's cached by cloudwatchd per script would be great too.

ghost assigned rremer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment