7

I've created a Fargate task that has a web server container. The task has an eni which appears to have a public IP. The container definition for the web server has port mapping for port 443. But when I inspect the container, network bindings are not configured. And I cannot access the web server using the public IP address. What am I missing?

enter image description here

Improve this question
3
  • Have you validate you're in a public subnet? And checked the container definitions are using the port mapping for the correct container Commented Oct 29, 2020 at 17:49
  • 3
    Yes to both of those. And I found the problem, I had not set the proper inbound rules on the security group associated with the ENI Commented Oct 30, 2020 at 18:02
  • 1
    Glad you solved it, have a great weekend :D Commented Oct 30, 2020 at 18:11

1 Answer 1

Reset to default
11

I needed to add the proper inbound rules for the security group associated with the ENI

Improve this answer
Sign up to request clarification or add additional context in comments.

4 Comments

what did you exactly do, I have the same problem...
this fixed it for me. from the tasks details, click on the ENI details and edit your inbound rules
Thanks a lot! this was the issue. I added a new rule to the security group to allow inbound traffic from "my ip address" and bingo- immediately see the public IP accessible.
@dotnetcoder, I did all you and OP did and still the public IP spins forever and then gives a site cannot be reached error. Did you copy public IPv4 straight into URL bar? With http or https protocol? I even tried the DNS name and adjusted inbound rules to my IP, all IPs, even sg id to no avail. Everything in ECS is green, "active" or "running" and yet I cannot launch any page!

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.