alexcasalboni/aws-lambda-power-tuning

Add KMS permission(s) that may be optionally needed

Open

#214 建立於 2023年9月20日

在 GitHub 查看
 (11 留言) (0 反應) (1 負責人)JavaScript (4,670 star) (325 fork)batch import
enhancementhelp wanted

描述

I had to create an IAM policy with kms:CreateGrant permission for the KMS key I was using with my Lambda functions, and then attach this manually to the solution's Lambda IAM roles.

It would be great to be able to optionally pass the KMS key ARN and add the necessary permission(s) as part of the solution.

貢獻者指南

技術棧
javascriptnodejsaws
領域
clouddevops
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
AWS IAM basicsKMS key managementCloudFormation templates
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
55
研究方向
The issue requests adding an optional KMS key ARN parameter to the solution's IAM policy generation. Review the existing CloudFormation template (likely at serverless.yml or template.yaml) to identify where IAM roles for Lambda are defined. Add a new optional parameter for KMS key ARN, and conditionally attach kms:CreateGrant permission to the Lambda execution roles. Check comments in the issue for any suggested implementation details or existing work.