aws / aws/containers-roadmap

[EKS] [request]: ebs encryption by default with cmk is not being applied

Open
#2,021 0 comments 0 reactions 0 assignees View on GitHub
EKS 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**
Applied for EBS volume encryption for CMK

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
CMK is applied to the volume, the node group cannot launch instances properly

**Are you currently working around this issue?**
Using the included KMS key from AWS

**Additional context**
No problem when creating instances separately

**Attachments**

Contributor guide

Open the contributing guide

Research direction

No repository file, test, or entry point is named. Start by reproducing EKS node-group creation with EBS encryption enabled using a customer-managed KMS key, compare it with the included AWS KMS key behavior, and verify that the node group launches instances successfully with the CMK-applied volumes.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.