<p>I have followed the AWS getting started guide to provision an EKS cluster (3 public subnets and 3 private subnets). After creating it, I get the following API server endpoint <a href="https://XXXXXXXXXXXXXXXXXXXX.gr7.us-east-2.eks.amazonaws.com" rel="nofollow noreferrer">https://XXXXXXXXXXXXXXXXXXXX.gr7.us-east-2.eks.amazonaws.com</a> (replaced the URL with X's for privacy reasons).</p>
<p>Accessing the URL in the browser I get the expected output from the cluster endpoint.</p>
<p>Question: How do I point my registered domain in Route 53 to my cluster endpoint?</p>
<p>I can't use a <code>cname</code> record because my domain is a root domain and will receive an apex domain error.</p>
<p>I don' have access to a static ip, and I don't believe my EKS cluster has a public IP address I can directly used. This would mean I can't use an A record (as I need an IP address).</p>
<p>Can I please get help/instructions as to how I can point my domain straight to my cluster?</p>
<p>Below is my AWS VPC architecture:</p>
<p><a href="https://i.stack.imgur.com/3Oc9g.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/3Oc9g.png" alt="enter image description here" /></a></p>

<p>Don't try and assign a pretty name to the API endpoint. Your cluster endpoint is the address that's used to talk to the control plane. When you configure your kubectl tool, the api endpoint is what kubectl talks to.</p>
<p>Once you've got an application running on your EKS cluster, and have a load balancer, or Ingress, or something for incoming connections, that's when you worry about creating pretty names.</p>
<p>And yes, If you're dealing with AWS load balancers, you don't get the option of A records, so you can't use the apex of the domain, unless you're hosting DNS in route 53, in which case, you can use &quot;alias&quot; records to point the apex of a domain at a load balancer.</p>
<p>Kubernetes is a massively complex thing to try understand and get running.  Given that this is the type of question you're asking, it sounds like you don't have the full picture yet. I recommend (1) joining the Kubenetes slack channel. It'll be a much faster way to get help than SO, and (2) take in Jeff Geerling's excellent Kubernetes 101 course on youtube.</p>
