Working with Microservices-15: Importing Amazon EKS cluster to Rancher in the Production Stage

We will import the Amazon EKS cluster that we created to Rancher by using Rancher menus. For this, we will prepare and assign a role and policy to the Rancher server in order to use AWS EKS resources. And, we will make the necessary change for the TLS certificate in “api-gateway” ingress file. Then we will check that the web address of application was working safely with HTTPS by using TLS/SSL certificate that we assigned it. We will do it all step by step.

Topics we will cover:

1. Preparing and Assigning a Role and Policy for the Rancher server

2. Importing the “microservice-app-eks” cluster to Rancher

3. Making the necessary change for the TLS certificate in “api-gateway Ingress file”

4. Clean up

5. As a result

6. Next post

7. References

1. Preparing and Assigning a Role and Policy for the Rancher server

Start the Rancher server and log in, in order to manage the Amazon EKS cluster from Rancher. If your Rancher Server is not installed, you can complete the Rancher Server installation by reading my article below.

Working with Microservices-6: Creating the Rancher server, Running Rancher in it, and Preparing…

Firstly, we will assign the necessary roles and policies to the Rancher server, for this navigate in Amazon console; EC2 >your Rancher server > Security tab > click on the “IAM role”, as shown in Picture-1.