ECS deployment failure due to ECR error?

Question

Hi, I started to see ECS deployment failure this afternoon. I'm not exactly sure why but i see this error under the ECS deployment page for the tasks that are being started

```
CannotPullContainerError: pull image manifest has been retried 5 time(s): Get "https://935480842411.dkr.ecr.us-west-2.amazonaws.com/v2/......
```

I see that there's an issue open under AWS Health Dashboard titled `ElasticContainerRegistry proxy v2 API latency issue`

Is that what's causing the server deployment failure? Seems like ECS just keeps retrying --  What can I do in this case?

Answer

Hello.

It appears that there are currently "Network Connectivity Issues" occurring in us-west-2.  
I think it is possible that access to ECR is failing due to network delay.  
Since this is an issue on the AWS side, I think it will be difficult for users to take countermeasures until it is fixed.

> [11:57 AM PDT] We can confirm increased networking latencies and errors affecting multiple Availability Zones (usw2-az1 and usw2-az2) in the US-WEST-2 Region. We have identified a potential root cause of the errors and are attempting mitigations. Early signs are this mitigation is reducing error rates and latencies. We continue to work towards a full root case and recovery.
> 
> [11:43 AM PDT] We are investigating increased networking latencies and errors affecting multiple Availability Zones (usw2-az1 and usw2-az2) in the US-WEST-2 Region.

The affected services are listed below.  
![ecs](/media/postImages/original/IM8EdJQY4HQRWJTNyMsVZUSA)

ECS deployment failure due to ECR error?

Contenus pertinents