EKS Domain

On AWS we recommend using a custom DNS name to access services in your Kubernetes cluster to ensure you can use all of your Availability Zones
If you do not have a custom DNS name you can use yet, then you can register a new one here: https://console.aws.amazon.com/route53/home?#DomainRegistration:
? Would you like to register a wildcard DNS ALIAS to point at this ELB address?  No

The Ingress address <snip>-dd0217b352d06378.elb.us-east-1.amazonaws.com is not an IP address. We recommend we try resolve it to a public IP address and use that for the domain to access services externally.
? Would you like wait and resolve this address to an IP address and use it for the domain? Yes

Waiting for <snip>-dd0217b352d06378.elb.us-east-1.amazonaws.com to be resolvable to an IP address...
WARNING: retrying after error: Address cannot be resolved yet <snip>-dd0217b352d06378.elb.us-east-1.amazonaws.com
.

<snip>-dd0217b352d06378.elb.us-east-1.amazonaws.com resolved to IP <snip>.202.15
You can now configure a wildcard DNS pointing to the new Load Balancer address <snip>.202.15
If you don't have a wildcard DNS setup then create a DNS (A) record and point it at: <snip>.202.15, then use the DNS domain in the next input...

If you do not have a custom domain setup yet, Ingress rules will be set for magic DNS nip.io.
Once you have a custom domain ready, you can update with the command jx upgrade ingress --cluster
? Domain <snip>.202.15.nip.io
nginx ingress controller installed and configured