# Install Rancher on AWS EKS
**URL:** https://forums.suse.com/t/install-rancher-on-aws-eks/11637
**Category:** SUSE Rancher Prime
**Created:** [August 29, 2018, 6:39pm UTC](https://forums.suse.com/t/install-rancher-on-aws-eks/11637 "2018-08-29T18:39:42Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@saverio](https://forums.suse.com/u/saverio)
#### Post date: [August 29, 2018, 6:39pm UTC](https://forums.suse.com/t/install-rancher-on-aws-eks/11637/1 "2018-08-29T18:39:42Z")
Is it possible/recommended to deploy rancher on an existing AWS EKS cluster so that it can run off of that, instead of managing it’s own EKS cluster? I haven’t seen any mention of this, but presumably it would make an HA installation a bit more available.
---
### Author:  [@chrisenytc](https://forums.suse.com/u/chrisenytc)
#### Post date: [August 31, 2018, 6:24am UTC](https://forums.suse.com/t/install-rancher-on-aws-eks/11637/2 "2018-08-31T06:24:59Z")
Would be awesome to use Rancher on EKS, that would make me more confident in running production workloads on Rancher. Unfortunatelly there’s no documentation for that. 😕
---
### Author:  [@stu2](https://forums.suse.com/u/stu2)
#### Post date: [September 5, 2018, 1:50am UTC](https://forums.suse.com/t/install-rancher-on-aws-eks/11637/3 "2018-09-05T01:50:23Z")
I’d like to do this too. Any guidance from others who’ve done this or from Rancher folks would be appreciated.
---
### Author:  [@Martin\_Higham](https://forums.suse.com/u/Martin_Higham)
#### Post date: [January 24, 2019, 3:16pm UTC](https://forums.suse.com/t/install-rancher-on-aws-eks/11637/4 "2019-01-24T15:16:49Z")
It’s a fairly straightforward process
I followed [https://eksworkshop.com/](https://eksworkshop.com/) to get my first EKS cluster setup and the right tools installed, including Helm.
I then installed an nginx ingress
```
helm install stable/nginx-ingress --name rancher-nginx --set rbac.create=true
```
and finally I followed the Rancher instructions for installation with Helm ([https://rancher.com/docs/rancher/v2.x/en/installation/ha/helm-rancher/](https://rancher.com/docs/rancher/v2.x/en/installation/ha/helm-rancher/)). In our case I used certificates from a file, ran Rancher in the same namespace as the ingress and had to specify the ingress class via ingress.extraAnnotations. e.g.
```
helm install rancher-stable/rancher --name rancher --set hostname=rancher.example.com --set ingress.tls.source=secret --set ingress.extraAnnotations."kubernetes\.io/ingress\.class"=nginx
```
---
### Author:  [@kescotOtaf](https://forums.suse.com/u/kescotOtaf)
#### Post date: [July 11, 2019, 5:31pm UTC](https://forums.suse.com/t/install-rancher-on-aws-eks/11637/5 "2019-07-11T17:31:25Z")
It is possible to run rancher from an existing EKS cluster, using helm to deploy as described. We are doing this for our dev environment. However, be aware that Rancher uses ECTD as its storage. As far as I am aware, AWS has not provided any access to the ECTD cluster, so you cannot backup/restore/migrate using default k8s tools.
You might be able to export all the relevant objects using kubectl, but I am not sure if this is actually possible yet. You would have to determine what are all the objects managed by rancher and hope to be able to export and import them into a new ectd cluster. We are looking at this for a migration, but not too seriously yet. I’d love to hear if anyone has a solution for this.
---
### Author:  [@yusran.ade](https://forums.suse.com/u/yusran.ade)
#### Post date: [December 26, 2021, 2:28pm UTC](https://forums.suse.com/t/install-rancher-on-aws-eks/11637/6 "2021-12-26T14:28:45Z")
> [@kescotOtaf](#):
>
> ironm
Awesome, may I know sir about your topology to running this rancher inside the EKS?
is it using Load Balancer?, since the pods rancher server installed inside Kubernetes managed host will be use the default ClusterIP in the service rancher.