- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Fargate is also recognized for use in private registries.
https://aws.amazon.com/jp/blogs/compute/introducing-private-registry-authentication-support-for-aws-fargate/
I thought "extra_hosts" in the following document might be relevant, since it seems that name resolution is not working.
https://github.com/ayufan/gitlab-ci-multi-runner/blob/master/docs/configuration/advanced-configuration.md
Hello Abdul,
Thank you for using AWS services.
Have you tried using VPC Endpoint ? I've recently experimented similar use-case to pull an image from Private ECR to my ECS Cluster, i was able to do so using the VPC Endpoint (My ECS Cluster was provisioned with Fargate as capacity Provider). While creating the VPCEndpoint, please make sure to enable Private DNS Name.
Reference: https://docs.aws.amazon.com/AmazonECR/latest/userguide/vpc-endpoints.html
Contenuto pertinente
AWS UFFICIALEAggiornata 3 anni fa- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
Thanks for the response. The article explains how we can setup private registries but does not provide any details if the registry can be in private network. extra_hosts variable seems to be container variable. My understanding is that the fargate host first pulls the image from the registry and then spins up the container, this variable comes into effect when the container is started. (I could be wrong). There might be a way to have the manipulate fargate hosts so it can talk to private registry on a private network. Maybe using private link but I am not sure if thats the right path. Thoughts?