aws / aws/aws-lambda-roadmap

Feature- Lambda Layer Alias

Open
#60 2 comments 16 reactions 0 assignees View on GitHub
Community request
Dominant language
No language data
Stars
196
Forks
5
PR merge metrics
No merged PRs in 30d

Description

**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**
Lambda Layers have hard coded version numbers. Sometimes I want to use an alias to point to a newer version of a layer. Please release lambda layer alias so I can move several functions at one time to a new lambda layer.

**Additional context**
N/A

Contributor guide

Open the contributing guide

Research direction

The issue mentions no repository files, tests, or entry points. Start by clarifying the expected Lambda Layer alias behavior and scope with maintainers, then identify the affected implementation and tests. Done should include an agreed design and verified support for moving functions between layer versions through an alias.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.