This message was deleted.

Did you run the command that Rancher generates for you on the EKS cluster? Usually you would need the eks-operator to be installed in order to establish communication back to Rancher. • https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/kubernetes-clusters-in[…]/set-up-clusters-from-hosted-kubernetes-providers/eks • https://ranchermanager.docs.rancher.com/reference-guides/cluster-configuration/rancher-server-configuration/sync-clusters

the eks cluster must also be able to contact your instance of rancher. it looks like you're running rancher on a

192.

address, so eks won't be able to 'phone home'. also, not sure if this is blocking, but the latest supported version of eks in the latest rancher is

v1.26.4-eks-0a21954

https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-7-5/

I had this issue before. Make sure you create proper IAM role and permission in your AWS account (ie. eks:*) , then also don’t forget to create ClusterRole and ClusterRoleBinding according to your IAM role