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

  • is there any firewall blocking the connection?

1 回答
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
已回答 2 年前
  • 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

  • Any update / resolution ??

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则