[Feature Request] External Registry - Add AWS ECR as option
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
I want to add aws_access_key_id and aws_secret_access_key from an IAM user to access AWS ECR.
Currently, I can use the username AWS along with the output of the AWS CLI command aws ecr get-login-password to get a temporary login that lasts for 12 hours.
If I want persistent access to AWS ECR, I need to configure the aws_access_key_id and aws_secret_access_key, similar to how it's done when using amazon-ecr-credential-helper in a Docker setup.
Describe the solution you'd like
able to select AWS Ecr to fill up aws_access_key_id and aws_secret_access_key
Describe alternatives you've considered
none.
Additional context
No response
Will you send a PR to implement it?
Maybe, need help
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by locating the external registry configuration and existing credential flows, then trace how registry options authenticate; done means AWS ECR is selectable and aws_access_key_id plus aws_secret_access_key provide persistent access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100