1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
Take a look at https://aws.amazon.com/blogs/devops/build-a-continuous-delivery-pipeline-for-your-container-images-with-amazon-ecr-as-source/
In particular, they obtain the credentials during a pre-build step:
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
what is the exact error?
there is no error message, just blocking undefinitely
we have the same here. context is : we are logging in from github action CI to ECR to push fresh built image. It worked last week and on thursday it started to hang indefinetly our CI with no error information / stack traces. We changed nothing on our credentials and architecture around ECR last week. We tried a telnet sucessfully to ECR, but it does not work from aws cli (hang indefinetly). What's more, cloud trail shows a successful connection attempt from our CI to ECR before hanging. Note: we work on AWS Ireland.
Same there, looks like and AWS internal issue not show on AWS Health monitor.