aws / aws/containers-roadmap

[lambda] [request]: Lambda should support tagging ENIs

Open
#1,924 0 comments 23 reactions 0 assignees View on GitHub
Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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 working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
It would be great if lambda functions would provide a setting which allows the propagation of their tags to created ENIs. Right now the tags are only applied to the function and ENIs which are automatically created for this function have no tags. The only way to tag these is to manually use the cli or management console which doesnt follow the principle of IaC.
A good example for this kind of property is the TagSpecification property on ec2 Launchtemplates, which allows to tag resources which get created and managed by AWS.

**Which service(s) is this request for?**
Lambda

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Since tags have various usecase for compliance and billing a solution for tagging would be really helpful.

**Are you currently working around this issue?**
A (maybe possible) workaround could be to use a custom resource which uses the awscli to add the tags to created enis when the stack containing the lambda function gets created or updated. For this to work you would need to find the right eni by using the describe-network-interfaces command first and filter the result for the ENI to tag.

Contributor guide

Open the contributing guide

Research direction

No repository file or test entry point is identified. Start by researching AWS Lambda ENI creation and comparing the requested behavior with EC2 LaunchTemplate TagSpecification; the issue considers AWS CLI describe-network-interfaces and a custom resource as workarounds. Done would mean a Lambda setting propagates function tags to its automatically created ENIs.

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
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.