serverless/serverless

Allow configuration of ECR repository encryption

Open

#9,083 创建于 2021年3月5日

在 GitHub 查看
 (5 评论) (0 反应) (0 负责人)JavaScript (46,915 star) (5,734 fork)batch import
cat/lambda-imageenhancementhelp wanted

描述

Use case description

When using Docker images in Lambda, Serverless automatically creates an ECR repository using the default encryption settings, meaning it must be manually managed to use a customer-managed KMS key for encryption.

Proposed solution

Add optional configuration of a customer-managed KMS key for the ECR repository through serverless.yml.

贡献者指南

技术栈
javascriptnodejs
领域
clouddevops
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Basic knowledge of Serverless FrameworkFamiliarity with AWS ECR and KMS
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
35
研究方向
Examine how the Serverless Framework creates ECR repositories, likely in the AWS packaging plugin (e.g., `lib/plugins/aws/package/compile/compileFunctions.js`). Look at the default encryption settings and how other infrastructure resources (like S3 buckets) allow custom KMS key configuration. Then propose a new configuration option in `serverless.yml` (e.g., under `provider.ecrRepositoryEncryption`) and implement the logic to pass the KMS key ID to the ECR repository creation API call. Ensure backward compatibility by defaulting to AWS managed keys if no configuration is provided.