<p>I'm new to EKS (but familiar with k8s), and I'm trying to run the my project on EKS.</p>
<p>I ran the my project deployment and the db deployment, and both are running:</p>
<pre><code>kubectl get deploy -owide
NAME   READY   UP-TO-DATE   AVAILABLE   AGE   CONTAINERS   IMAGES             SELECTOR
my-app   1/1     1            1           98m   my-app         me/my-app:latest   app=my-app
db     1/1     1            1           16h   db           mariadb:10.4.12    app=db
</code></pre>
<p>And I created loadbalancer to reach the my-app pods:</p>
<pre><code>get svc -owide
NAME         TYPE           CLUSTER-IP       EXTERNAL-IP                                                               PORT(S)          AGE    SELECTOR
my-app         LoadBalancer   10.102.XXX.XXX   XXX-XXX.us-east-1.elb.amazonaws.com   8000:31722/TCP   114m   app=my-app
kubernetes   ClusterIP      10.102.0.1       &lt;none&gt;                                                                    443/TCP          39h    &lt;none&gt;
</code></pre>
<p>I tried to reach to the website via the external ip created by the loadbalancer (XXX-XXX.us-east-1.elb.amazonaws.com), with the port (I tried 80, 8000 and 31722), and I get &quot;the site can't be reached&quot;.</p>
<p>Do I miss something?</p>
<p>This is the my-app service:</p>
<pre><code>apiVersion: v1
kind: Service
metadata:
  name: my-app
spec:
  type: LoadBalancer
  ports:
  - name: &quot;8000&quot;
    port: 8000
    targetPort: 8000
  selector:
    app: my-app
</code></pre>
<p>This is the my-app yaml:</p>
<pre><code>apiVersion: apps/v1
kind: Deployment
metadata:
  name: my-app-deployment
  labels:
    app: my-app
  name: my-app
spec:
  replicas: 1
  selector:
    matchLabels:
      app: my-app
  template:
    metadata:
      labels:
        app: my-app
    spec:
      containers:
      - env:
        - name: REVERSE_PROXY
          value: &quot;true&quot;
        - name: UPLOAD_FOLDER
          value: /var/uploads
        - name: WORKERS
          value: &quot;1&quot;
        image: me/my-app:latest
        imagePullPolicy: &quot;&quot;
        name: my-app
        ports:
        - containerPort: 8000
        resources: {}
      restartPolicy: Always
      serviceAccountName: &quot;&quot;
</code></pre>

Yagel
<p>I would suggest following steps to find root-cause;</p>
<ol>
<li><p>Check whether laod balancer's XXX-XXX.us-east-1.elb.amazonaws.com domain is reachable from the host/machine you are trying to access. You can use ping command to check network reachability from your host/machine/laptop/desktop.</p>
</li>
<li><p>If step 1 is successfully executed then, Check in default cloudwatch metrics for your load balancer. Please refer <a href="https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-cloudwatch-metrics.html#view-metric-data" rel="nofollow noreferrer">this</a> document about viewing  cloudwatch metrics through AWS web console. You can check any unusable error counts in this metrics.</p>
</li>
<li><p>If you did not find any useful information in the Step2 and if you have enabled VPC Flow Logs, then you can trace vpc flow logs to check, what is the problem with network traffic to &amp; from the AWS load balancer. For VPC flow logs information please refer <a href="https://aws.amazon.com/blogs/aws/vpc-flow-logs-log-and-view-network-traffic-flows/" rel="nofollow noreferrer">this</a> document from AWS.</p>
</li>
</ol>
