aws / aws/containers-roadmap

[ECS] [request]: public IPs for awsvpc

Open
#423 3 comments 25 reactions 0 assignees View on GitHub
ECS Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

**Tell us about your request**

Allow an awsvpc ENI to have a public IP address or elastic IP.

**Which service(s) is this request for?**

ECS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**

I want to have both the security features of awsvpc networking and public internet access.

I prefer not to have the complexity, cost, performance, or availability limitations of an NAT gateway.

**Are you currently working around this issue?**

Workarounds:

* Set up a NAT gatway
* Use Fargate
* Use host or bridge networking

**Additional context**

Fargate has had public IPs for awsvpc ENIs from day 1. Presumably it wouldn't be hard to add this for EC2-based containers.

Contributor guide

Open the contributing guide

Research direction

This is an ECS roadmap request rather than a repository implementation task. Start by reviewing the awsvpc networking request, its listed workarounds, and the stated Fargate precedent. Done means EC2-based ECS awsvpc ENIs can receive a public or elastic IP without requiring the listed NAT gateway workaround.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.