[ECR] [request]: Have the service retire KMS grants on repo deletion
- 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**
ECR now supports KMS encryption. Using it causes an error on deletion, where the service doesn't retire the KMS grant and tries to use the role to do so, which isn't congruent with other services and requires unreasonable permissions _or_ manual cleanup.
**Which service(s) is this request for?**
ECR
Contributor guide
Research direction
No implementation files, tests, or entry points are identified. Start by reviewing how ECR handles KMS-encrypted repositories during deletion and compare its grant-retirement behavior with other services; done means repository deletion retires the KMS grant without requiring unreasonable permissions or manual cleanup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 15/100