Skip to content
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

Automatically shut down cfn-pilosa cluster after configurable TTL #1

Closed
codysoyland opened this issue Dec 16, 2016 · 2 comments
Closed

Automatically shut down cfn-pilosa cluster after configurable TTL #1

codysoyland opened this issue Dec 16, 2016 · 2 comments
Assignees
@codysoyland

Comments

@codysoyland
Copy link
Contributor

No description provided.

@codysoyland codysoyland self-assigned this Dec 16, 2016
@codysoyland
Copy link
Contributor Author

This is proving to be more difficult than anticipated. AWS has a blog post that shows a method of doing this: https://aws.amazon.com/blogs/devops/scheduling-automatic-deletion-of-application-environments/

But the AWS method requires use of an EC2 instance with the cfn tools installed (such as Amazon Linux) and I would like to avoid having extra software installed on the pilosa machines. I would like to use Lambda to schedule the deletion, but I haven't found a clear way to schedule a lambda job.

I will Icebox this for now and we can discuss options in the future.

@codysoyland
Copy link
Contributor Author

Issue moved to pilosa/infrastructure #2 via ZenHub

@codysoyland codysoyland mentioned this issue Jul 5, 2017
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@codysoyland codysoyland

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@codysoyland