# How to SSH into EKS cluster

**URL:** <https://forums.suse.com/t/how-to-ssh-into-eks-cluster/14251>\
**Category:** General\
**Created:** [May 13, 2019, 9:48pm UTC](https://forums.suse.com/t/how-to-ssh-into-eks-cluster/14251 "2019-05-13T21:48:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stephen\_Jensen1](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/stephen_jensen1/32/5185_2.png) [@Stephen\_Jensen1](https://forums.suse.com/u/Stephen_Jensen1)\
**Post date:** [May 13, 2019, 9:48pm UTC](https://forums.suse.com/t/how-to-ssh-into-eks-cluster/14251/1 "2019-05-13T21:48:01Z")

</div>

I created an EKS cluster using rancher. Everything spun up fine and I’d like to download the SSH key that rancher created for my nodes. When I go to the Nodes tab and click on a node, I don’t see an option to download the keys. I saw in another support forum that I should see this option here, what am I missing?

 ![41%20PM](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/8/8742594b9b19e232ba1a29866d40f487d69dc524.png)

---

<div class="post-metadata">

**Author:** ![mattia.orsi](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/mattia.orsi/32/7429_2.png) [@mattia.orsi](https://forums.suse.com/u/mattia.orsi)\
**Post date:** [April 6, 2021, 1:45pm UTC](https://forums.suse.com/t/how-to-ssh-into-eks-cluster/14251/2 "2021-04-06T13:45:49Z")

</div>

Hello Stephen … did you find a solution? i have the same problem.

---

<div class="post-metadata">

**Author:** ![Bruce.lee](https://avatars.discourse-cdn.com/v4/letter/b/ac91a4/32.png) [@Bruce.lee](https://forums.suse.com/u/Bruce.lee)\
**Post date:** [June 3, 2021, 11:57pm UTC](https://forums.suse.com/t/how-to-ssh-into-eks-cluster/14251/3 "2021-06-03T23:57:32Z")

</div>

I hope this helps everyone reading this.

Problem: Unknown Hang between SSH connections.

Resolution: If created by Default during template creation in EKS, it must  
If you look at the inbound rules, it seems that there is no problem, of course, as it is set as a whole.  
This is a trap…  
We need to set “Anywhere” in the “source” part of the inbound rule.

The default user between SSH connections is ec2-user.

Clearance:  
ssh user —\> ec2-user  
Solved ----------\> Modify the “source” part of the security group network inbound rule

 ![test](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/e/e01cbb7034d4111e7f9ce7c43bc35ff53be41443.png)