# Cannot add credentials for ECR container registry

**URL:** <https://community.seqera.io/t/cannot-add-credentials-for-ecr-container-registry/1395>\
**Category:** Ask for help\
**Tags:** wave, aws, platform\
**Created:** [November 11, 2024, 2:52pm UTC](https://community.seqera.io/t/cannot-add-credentials-for-ecr-container-registry/1395 "2024-11-11T14:52:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tom\_Schoonjans](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/tom_schoonjans/32/1218_2.png) [@Tom\_Schoonjans](https://community.seqera.io/u/Tom_Schoonjans)\
**Post date:** [November 11, 2024, 2:52pm UTC](https://community.seqera.io/t/cannot-add-credentials-for-ecr-container-registry/1395/1 "2024-11-11T14:52:44Z")

</div>

Hi all,

I would like to test running wave containers in AWS Batch using images hosted in a private ECR repository.

When trying to [add](https://docs.seqera.io/platform/24.1/credentials/aws_registry_credentials) new user credentials for my IAM user that I created specifically for this purpose, I get at the end:

> Unexpected error while processing request - Error ID: DYrdRT1bFglVGY8Az8vDd

I have confirmed locally that with the access/secret key created for this user I can access the private ECR repository.

Any thoughts on what’s going on here?

---

<div class="post-metadata">

**Author:** ![mribeirodantas](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/mribeirodantas/32/235_2.png) [@mribeirodantas](https://community.seqera.io/u/mribeirodantas)\
**Post date:** [November 14, 2024, 11:50pm UTC](https://community.seqera.io/t/cannot-add-credentials-for-ecr-container-registry/1395/2 "2024-11-14T23:50:04Z")

</div>

Hi @Tom_Schoonjans. Welcome to the forum!

Can you share a minimal reproducible example?

Are you running this on Seqera Enterprise or Seqera Cloud?

---

<div class="post-metadata">

**Author:** ![Tom\_Schoonjans](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/tom_schoonjans/32/1218_2.png) [@Tom\_Schoonjans](https://community.seqera.io/u/Tom_Schoonjans)\
**Post date:** [November 15, 2024, 8:35am UTC](https://community.seqera.io/t/cannot-add-credentials-for-ecr-container-registry/1395/3 "2024-11-15T08:35:26Z")

</div>

Hi Marcel,

I observed this on Seqera Cloud. I basically followed the instructions found at [AWS ECR credentials | Seqera Docs](https://docs.seqera.io/platform/24.1/credentials/aws_registry_credentials#add-credentials-to-seqera).

Tested this with both Safari and Firefox.

I was in a call yesterday with your colleague Mark Panganiban, and he managed to reproduce this on his machine as well.

---

<div class="post-metadata">

**Author:** ![mribeirodantas](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/mribeirodantas/32/235_2.png) [@mribeirodantas](https://community.seqera.io/u/mribeirodantas)\
**Post date:** [November 15, 2024, 8:20pm UTC](https://community.seqera.io/t/cannot-add-credentials-for-ecr-container-registry/1395/4 "2024-11-15T20:20:02Z")

</div>

Hi Tom,

I just discussed this with Mark and he told me it was a bug indeed. It was fixed and you messaged us earlier today saying it’s working now. Thanks for the feedback.