Fargate tasks: ability to set a proxy to be used

### Summary Feature request for Fargate tasks: ability to set a proxy to be used for pulling Docker images and automatically set the proxy env variables inside containers (as per https://docs.docker.com/network/proxy/#configure-the-docker-client) ### Description In environments where security is paramount it is very common to have to use a proxy for all outbound Internet traffic. Given AWS ECR currently doesn't offer a VPC endpoint, pulling images from it requires an Internet connection. It's possible to set such a proxy configuration using EC2 ECS tasks, but not when running Fargate tasks (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/AWS_Fargate.html#fargate-tasks-services-networking). Also of great usefulness would be if this proxy configuration would automatically propagate into launched containers of a Fargate task. EDIT: There's now support for ECR on PrivateLink: https://aws.amazon.com/about-aws/whats-new/2019/01/aws-fargate--amazon-ecs--and-amazon-ecr-now-have-support-for-aws/, so this issue is only relevant for people wishing to use private repositories other than ECR.

Posted by ricoli on Jul 12, 2018, 2:00 PM

Tags

• support (Network)

Related issues

• That Reddit post is feeding more conspiracy thinking than helping.
• Support BYOK/Custom Models for Inline Code Completions
• DNS-PERSIST-01 challenge support (planned for late Q1 2026)
• Yeah I can't really blame people for not realising they have shitty mics and shitty internet because it's really hard for them to tell!
• Onboarding guide for FluentAssertions
• Add WebTransport support