Lifecycle policies for Lambda Resources

Open
#36 0 comments 14 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws
Domain
cloud

Research direction

This is an exploratory request about lifecycle policies for versioned Lambda resources, including maximum-version, last-invoked, timestamp, status, and dependency rules. No files, tests, implementation entry points, or completion criteria are identified; the issue currently seeks community feedback rather than defining a startable change.

Written by the indexing model from the issue text.

Description

Lambda PM request Lambda/Governance

Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request
    If you are interested in providing additional feedback, please leave a comment

Description
We are exploring supporting lifecycle policies for versioned Lambda resources. With this feature, customers could delete multiple versions at once via a retention policy. We are exploring "max versions", "last invoked", and other qualifiers to automatically delete versions that do not match the policy when you create a new version or update a resource.

Additional context

  1. What types of actions would you want to take, for example, label a function as deprecated, delete a layer version, block invokes, etc.?
  2. What types of timestamp based rules would you write, for example, 1 year after function version create date do x.
  3. Are there any other attributes you would want to reference in your policy?
  4. Do you need to write policies to delete resources based on the status of other resources, for example, delete all function versions that reference outdated runtimes?
  5. How would you want to handle dependencies for example, would you want to automatically delete function versions associated with a specific layer version?
Dominant language
No language data
Stars
196
Forks
5
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/aws-lambda-roadmap

All issues in aws/aws-lambda-roadmap

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.