# ECR docker registry authentication issue with CloudQuery

**URL:** <https://community.cloudquery.io/t/ecr-docker-registry-authentication-issue-with-cloudquery/464>\
**Category:** CloudQuery Plugins\
**Created:** [January 8, 2024, 1:52pm UTC](https://community.cloudquery.io/t/ecr-docker-registry-authentication-issue-with-cloudquery/464 "2024-01-08T13:52:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![special-glider](https://avatars.discourse-cdn.com/v4/letter/s/cc9497/32.png) [@special-glider](https://community.cloudquery.io/u/special-glider)\
**Post date:** [January 8, 2024, 1:52pm UTC](https://community.cloudquery.io/t/ecr-docker-registry-authentication-issue-with-cloudquery/464/1 "2024-01-08T13:52:05Z")

</div>

Hi,

Is ECR a supported Docker registry?

```yaml
registry: "docker"
path: "xxxx.dkr.ecr.eu-west-1.amazonaws.com/cq_sophos"

```

When I do that, I get the following error:

```auto
Error: failed to pull Docker image: Error response from daemon: Head "https://xxx.dkr.ecr.eu-west-1.amazonaws.com/v2/cq_sophos/manifests/latest": no basic auth credentials

```

I can, however, do a `docker pull xxx.dkr.ecr.eu-west-1.amazonaws.com/cq_sophos`, and that works fine. I can get around this by pulling the image before running `cq` if I have to. I have also set the default region to see if that was the cause, but no joy.

---

<div class="post-metadata">

**Author:** ![kemal](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/kemal/32/42_2.png) [@kemal](https://community.cloudquery.io/u/kemal)\
**Post date:** [January 8, 2024, 2:28pm UTC](https://community.cloudquery.io/t/ecr-docker-registry-authentication-issue-with-cloudquery/464/2 "2024-01-08T14:28:15Z")

</div>

Hi, currently only public Docker images are supported. We’re also in the process of adding support for pulling Docker images from `hub.cloudquery.io`.

Quickly checking, it looks like we need to add a way to support basic auth credentials for this to work (barring a full-blown ECR integration).

Could you open an issue for a feature request for this at [https://github.com/cloudquery/cloudquery/issues/new?assignees=&labels=kind%2Ffeat&projects=&template=feature\_request.yml&title=feat%3A+%3Ctitle%3E](https://github.com/cloudquery/cloudquery/issues/new?assignees=&labels=kind%2Ffeat&projects=&template=feature_request.yml&title=feat%3A+%3Ctitle%3E) which would help our team prioritize?

---

<div class="post-metadata">

**Author:** ![special-glider](https://avatars.discourse-cdn.com/v4/letter/s/cc9497/32.png) [@special-glider](https://community.cloudquery.io/u/special-glider)\
**Post date:** [January 8, 2024, 2:33pm UTC](https://community.cloudquery.io/t/ecr-docker-registry-authentication-issue-with-cloudquery/464/3 "2024-01-08T14:33:21Z")

</div>

Thanks for the reply, no prob will raise a ticket.  
[https://github.com/cloudquery/cloudquery/issues/16120](https://github.com/cloudquery/cloudquery/issues/16120)