To enable external access from the Internet to your apps deployed on the EKS cluster, you need to setup an NGINX ingress controller.
For this purpose, we provide a ready-made template that you can deploy in a few simple steps.
In the starting screen, select the Amazon EKS NGINX Ingress template, in the Free Application Templates section. You will be redirected to a page where you need to configure the necessary parameters, choose the cluster in which to deploy and trigger the deploy action.
As a first step, you need to connect a Git account (GitHub, Bitbucket, or GitLab). Microtica defines a repository name by default for each template, but you can change it. If you already have a Git account connected to Microtica, you can choose it from the list. We will create a new repository on your account with the provided name, and every Git push will be deployed automatically in Microtica.
In this step you need to provide the TLS certificate for the ingress.
The certificate body should be provided encoded in Base64 format.
Let's say you have the tls.crt and tls.key files containing the certificate body, you can encode the content using the following Shell commands:
Paste the command outputs in the template configuration.
You can provide a certificate from basically any type of certificate provider (e.g. Let's Encypt).
Next you would need to select the cluster to deploy the NGINX ingress on.
Choose a cluster and cluster namespace and click Save.
Once you’re done with the configuration and cluster selection, you can go ahead and trigger a deployment of the application by clicking on Deploy.
Once the deployment is completed, you can see the status of the application in Environment -> Apps.
The last step is to update your DNS records.
To do that, login into your AWS console -> EC2 -> Load Balancers. Use the DNS name of the load balancer to create new DNS record:
myapp.domain.com CNAME <load balancer DNS name>