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

トピック
計算するネットワークとコンテンツ配信コンテナ
タグ
Amazon EC2ネットワークとコンテンツ配信Amazon Elastic Container Serviceセキュリティグループ
言語
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 ??

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ