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.

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

Add functionality for tearing down inactive resources. #24

Open
sharkinsspatial opened this issue Apr 18, 2023 · 1 comment
Open

Add functionality for tearing down inactive resources. #24

sharkinsspatial opened this issue Apr 18, 2023 · 1 comment
Assignees

Comments

@sharkinsspatial
Copy link
Member

The current Lambda stack contains both single use resources and chunk based cron jobs which should be disabled after they have processed a complete inventory. Both these resources should be removed by some process after they no longer need to execute.

@sharkinsspatial
Copy link
Member Author

This is actually even more relevant given the fact that our AWSCustomResources use Cloudformation hooks internally and these are limited to 100 per account. We should include a base class for our functions that will be targets for InvokeFunction that includes logic to self-destruct. 😸

@sharkinsspatial sharkinsspatial self-assigned this Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant