AWS re:Post을(를) 사용하면 다음에 동의하게 됩니다. AWS re:Post 이용 약관
AWS re:Postre: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

  • AWS-User-13413
    2년 전

    is there any firewall blocking the connection?

주제
컴퓨팅네트워킹 및 콘텐츠 전송컨테이너
태그
아마존 EC2네트워킹 및 콘텐츠 전송아마존 엘라스틱 컨테이너 서비스보안 그룹
언어
English
AWS-User-8127861
질문됨 2년 전647회 조회
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
Nathan_W
답변함 2년 전
  • AWS-User-8127861
    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

  • AWS-User-8127861
    2년 전

    Any update / resolution ??

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠