Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Connection refused by public ip address, although image pulled from ECR running appropriately in pod container

0

Getting Connection refused by public ip address, although image pulled from ECR running appropriately in pod container. Security Group >>Inbound Group >>Type: HTTP, SSH, TCP, Port: 80, 22, 0-65535 all allowed for IPv4, even assigned Elastic IP to NAT Gateway which is allowing Public Ip through Internet Gateway

  • Uma Shankar
    5 years ago

    is there any firewall blocking the connection?

Topics
ComputeContainersNetworking & Content Delivery
Tags
Amazon EC2Amazon Elastic Container ServiceSecurity GroupNetworking & Content Delivery
Language
English

asked 5 years ago932 views

1 Answer
0

Does your VPC have an internet gateway? Are any other endpoints able to communicate publicly? Are you using any load balancers or network firewalls? When I was beginning with this service, I found this tutorial to be very helpful.

AWS

answered 5 years ago

  • AWS-User-8127861
    5 years ago

    Thanks Nathan, Tutorial is indeed very wonderful... while its more of ECR and ECS, while I require is image running on Elastic Kubernetes Services (EKS) in Pods Container, which is having VPC with Internet gateway and load balancers / auto scale is automatically taken by Elastic Kubernetes Services (EKS) Cluster/Pod,. While my requirement is App URL of Public IP is giving Connection refused... had there any problem with Pod Containers, it would have got evicted / terminated... I have given 8 Gibs Memory / 4 vCPU to each Pod and even enabled Inbound Rules in Security Groups

  • AWS-User-8127861
    5 years ago

    Any update / resolution ??

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content