<p>eks server endpoint is <strong>xxxxxxxxxxx.xxx.eks.amazonaws.com</strong> and I've created a yml file with a deployment and service object.  </p>

<pre><code>[ec2-user@ip-]$ kubectl get svc
NAME         TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE
fakeserver   NodePort    10.100.235.246   &lt;none&gt;        6311:30002/TCP   1h
kubernetes   ClusterIP   10.100.0.1       &lt;none&gt;        443/TCP          1d
</code></pre>

<p>When I browse <strong>xxxxxxxxxxx.xxx.eks.amazonaws.com:30002</strong> returns too long to respond. security groups have all traffic in inbound rules. </p>

<p>You should be using your Worker Node's IP (one of the nodes if you have more than one), not the EKS server endpoint. The EKS server endpoint is the master plane, meant to process requests pertaining to creating/deleting pods, etc.</p>

<p>You also need to make sure that the Security Group of your Node's will allow the traffic.</p>

<p>With this in place you should be able to make the request to your NodePort service.
For Example:</p>

<p><a href="http://your-workernodeIp:NodePortNumber" rel="nofollow noreferrer">http://your-workernodeIp:NodePortNumber</a></p>
