Creating a DNS entry for the ELB hostname in Route53

This section describes the steps to configure hostnames specified in the values.yaml file of the Helm chart for resolving the hostname of the Elastic Load Balancer (ELB) that is created by the NGINX Ingress Controller.

1. Configure Route53 for DNS resolution.

   • Create a private hosted zone in the Route53 service.
   • In our case, the domain name for the hosted zone is protegrity.com.
   • Select the VPC where the Kubernetes cluster is created.

2. Create a hostname for the ELB in the private hosted zone created in step 1.

   • Create a Record Set with type A - Ipv4 address
   • Select Alias as yes
   • Specify the Alias Target to the ELB created by the Nginx Ingress Controller

3. Save the record Create Inbound endpoint for DNS queries from a network to the hosted VPC used in Kubernetes.

   • Select Configure endpoints in the Route53 Resolver service.
   • Select Inbound Only endpoint.
   • Give a name to the endpoint.
   • Select the VPC used in the Kubernetes cluster and Route53 private hosted zone.
   • Select the availability zone as per the subnet.
   • Review and create the endpoint.
   • Note the IP addresses from the Inbound endpoint page.
   • Send CURL request to the hostname created using the Route 53 service

For more information about Amazon Route53, refer to Amazon Route53 Documentation.