[ECR] [request]: Ability to enable KMS Encryption on repos after creation
- 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**
With ECR, you can only enable KMS encryption on a repository during its creation. I am proposing for the ability to add KMS encryption after a repository's creation.
**Which service(s) is this request for?**
ECR
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
I have a customer who wanted to enable KMS Encryption to all the company's repositories. There are hundreds of images per repository and quite a bit of repositories as well. Because ECR doesn't have the ability to add KMS Encryption after the fact, my customer now has to manually create new repositories and transfer over the hundreds of images, all just to add the KMS Encryption feature. This is an inconvenient and time consuming solution for the customer to be able to use our KMS Encryption.
**Are you currently working around this issue?**
The customer will be manually creating new repositories as a workaround.
**Additional context**
Adding the ability or giving customers a more efficient workaround.
**Attachments**
Contributor guide
Research direction
No repository files, entry points, or tests are named. Start by reviewing the ECR repository encryption API and its constraints, then determine whether existing repositories can support changing encryption settings without moving images. Done means ECR provides an approved way to enable KMS encryption after repository creation, or documents an efficient supported workaround.
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