alexcasalboni/aws-lambda-power-tuning

Add KMS permission(s) that may be optionally needed

Open

#214 opened on Sep 20, 2023

View on GitHub
 (11 comments) (0 reactions) (1 assignee)JavaScript (4,670 stars) (325 forks)batch import
enhancementhelp wanted

Description

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.

Contributor guide

Tech stack
javascriptnodejsaws
Domain
clouddevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
AWS IAM basicsKMS key managementCloudFormation templates
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
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.