New workflow submission - Cleanup Lambda versions using Step Functions #376
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
This workflow shows how to manage/cleanup the number of available versions of an AWS Lambda function. The workflow uses the
ListFunctions
,ListVersionsByFunction
andDeleteFunction
SDK calls to determine which functions should be processed as well as to get to know the available number of versions and to reduce them to a specified amount. The workflow takes Lambda aliases into account as well as provides the possibility to filter which functions should be taken into account and how many versions - starting from the most recent one - should be kept available.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.