-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Amazon ECR Docker Credential Helper #676
Comments
I don’t see why not |
I got a PR started (#763). I'm not sure if it's the correct approach, but it's a start. We'd like to explore this as maintaining a cache between steps would help us not run into rate limits occasionally as well as speed things up. It also means we don't need to know all the ECR registry IDS ahead of time or put them explicitly in a separate plugin definition in our steps. |
At the moment if the We could work around this:
We're working on (3) by getting this behaviour changed in the ecr-helper itself (awslabs/amazon-ecr-credential-helper#847) This should allow for the elastic stack to install the helper in the base AMI, and optionally allow it to be configured in the Docker I recommend configuring it for an allow list of ECR repos, rather than as the default. Configuring It would be better to install it for an allow list of repositories, like: "credHelpers": {
"<account_id_here>.dkr.ecr.us-west-2.amazonaws.com": "ecr-login",
"public.ecr.aws": "ecr-login"
}, This could perhaps be configured in the Elastic stack parameters, or become part of the default |
AWS have just released v0.9.0 with the referenced issue fixed. This means that if the environment variable For Culture Amp builds at the moment we install the plugin by default and allow builds to opt-in to use it (because of the compatibility issue). If a build exposes an Now, though, we can enable it by default and start removing references to the ECR login from our pipelines. If this were to be included in the Elastic Stack:
Expand for
|
We could perhaps use this instead of the ECR plugin:
https://github.com/awslabs/amazon-ecr-credential-helper
I think it would be a more elegant solution, but there might be other considerations…?
The text was updated successfully, but these errors were encountered: