2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
I changed the region from eu-central-1
to us-east-1
following the same steps as I described above and it works. Probably there is some bug in AWS, hard to say if eu-central-1
can't access public.ecr.aws
or if it's something different.
con risposta 8 mesi fa
0
Hello.
I'm getting a timeout error when pulling the container image.
If the subnet used by ECS is a private subnet, try adding a route to the NAT Gateway to the route table or setting up a VPC endpoint for ECR.
https://docs.aws.amazon.com/AmazonECR/latest/userguide/vpc-endpoints.html
If you are using a public subnet, please check whether the subnet's public IP allocation is enabled.
https://docs.aws.amazon.com/vpc/latest/userguide/modify-subnets.html#subnet-public-ip
Contenuto pertinente
- AWS UFFICIALEAggiornata 4 mesi fa
- AWS UFFICIALEAggiornata 10 mesi fa
- AWS UFFICIALEAggiornata 2 anni fa
Hello. Unfortunately, creating a VPC endpoint for ECR or public NAT with a private subnet didn't help. All public subnets have
Enable auto-assign public IPv4 addressInfo
checked. I've already sent feedback to AWS that their guide is inaccurate or incomplete.If there's someone who could write me a step-by-step guide on how to make the below AWS guide work, that would be great: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/getting-started-fargate.html