aws / aws/containers-roadmap

[ECS,Fargate] [request]: Attach specific ENIs

Open
#558 6 comments 22 reactions 0 assignees View on GitHub
ECS Fargate
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

**Tell us about your request
What do you want us to build?**

Using Cloudformation when creating an ECS service for Fargate I'd like to be able to provide a list of Elastic Network Interfaces (ENI) for the Network Configuration such that the Fargate ran container will have consistent IPs.

**Which service(s) is this request for?**
Fargate/ECS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.**

We have a 3rd party server that we connect to over an AWS managed VPN. This 3rd party service requires that the client making the request (i.e. the fargate container) be a whitelisted IP in their Access Control List (ACL) and cannot whitelist multiple /28.

**Are you currently working around this issue?
How are you currently solving this problem?**

Creating dummy ENIs in each subnet to "reserve" non-whitelisted IPs such that the Fargate container will receive one of the "available" IPs that is a whitelisted IP. The other option is to not use Fargate and use traditional ECS whereby we attach ENIs to the managed EC2 instances.

Contributor guide

Open the contributing guide

Research direction

Start with the ECS/Fargate service Network Configuration and its CloudFormation representation, focusing on how ENIs are selected for a service. Done means a service can receive a specified list of ENIs so its Fargate tasks use consistent, whitelisted IP addresses.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.