# AWS ECR scanning and vulnerabilities concern for docker image 8.12.2

**URL:** <https://discuss.elastic.co/t/aws-ecr-scanning-and-vulnerabilities-concern-for-docker-image-8-12-2/368117>\
**Category:** Synthetics\
**Tags:** docker\
**Created:** [October 2, 2024, 6:45am UTC](https://discuss.elastic.co/t/aws-ecr-scanning-and-vulnerabilities-concern-for-docker-image-8-12-2/368117 "2024-10-02T06:45:28Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![xyngfei](https://avatars.discourse-cdn.com/v4/letter/x/a88e57/32.png) [@xyngfei](https://discuss.elastic.co/u/xyngfei)\
**Post date:** [October 2, 2024, 6:45am UTC](https://discuss.elastic.co/t/aws-ecr-scanning-and-vulnerabilities-concern-for-docker-image-8-12-2/368117/1 "2024-10-02T06:45:29Z")

</div>

I am trying to follow the [guide](https://www.elastic.co/guide/en/observability/8.12/synthetics-private-location.html#synthetics-private-location-connect) to pull the docker image, why are there so many critical findings? need some advice to move forward.

`docker pull docker.elastic.co/beats/elastic-agent-complete:8.12.2`

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/0/d0bfca54b9ef96580dbf1e5fb1ff0bddea77869e.png)