πŸ“œ
Our Manifesto
🧰
Backup & Disaster Recovery
πŸ‘¨β€πŸ‘©β€πŸ‘§β€πŸ‘¦ Customer Success & Supporty
πŸ‘¨β€πŸ‘©β€πŸ‘§β€πŸ‘¦ Community
Powered By GitBook
Make Public ELB to Private

Prerequisites

The following components must be installed and set up on your system and AWS account before you can get started with Amazon EKS:
Kubectl instructions AWS management console with EKS GUI access AWS CLI instructions DNS Manager access to update the CNAME entry

Step 1: Change the cluster endpoint access type to Private

    1.
    2.
    Go to cluster view(Amazon EKS) >> Select the Atlan cluster name >> Go to Configuration tab >> Select the Network tab >> Click on Manage Networking.
cluster-conf
    1.
    Change the cluster Endpoint Access to Private and save the changes.

Step 2: Change the load balancer type to internal from release portal

    1.
    Open the Atlan admin portal(release portal).
    2.
    Go to config section >> Advanced Options >> Enable the box for Deploy Internal Type Load Balancer >> save config.
release-portal-internal
    1.
    Deploy the latest release.

Step 3: Access the cluster from CLI and redeploy the services.

    1.
    Delete the nginx-ingress-controller(Product URL ELB) service from the below command.
    kubectl delete svc nginx-ingress-controller -n nginx-ingress
    2.
    Delete the kotsadm service from below command
    kubectl delete svc kotsadm-ui -n kots
    3.
    Redeploy the kostsadm-ui services again through below command. a. Export the kotsadm-ui deployment file to your system with the below command:
    kubectl get svc kotsadm-ui -n kots -o yaml > kotsadm-ui.yaml
    b. Redeploy the kotsadm-ui services again kubectl apply -f kotsadm-ui.yaml
kubectl-svc-output
    1.
    Now find the ELB's ARN value for DNS mapping.
    a. For Product URL: run the following command
    1
    `kubectl get svc -n nginx-ingress`
    Copied!
    ​
    ​
    b. For release portal URL run the following command.
    kubectl get svc -n kots
    ​
    ​
    2.
    Update the DNS setting(CNAME) in DNS manager(hosting provider) and allow 2-3 hours to propagate this.
Last modified 3d ago