AWS EKS is binding MC to a DNS name

When you deploy hazelcast chart to AWS EKS, the instructions provided in INDEX.txt was not correct for Management Center so I had to find out MC URL by executing describe command.

please see ``LoadBalancer Ingress` below.

```
$ kubectl describe svc dining-serval-hazelcast-enterprise-mancenter
Name: dining-serval-hazelcast-enterprise-mancenter
Namespace: default
Labels: app=hazelcast-enterprise
chart=hazelcast-enterprise-1.0.1
heritage=Tiller
release=dining-serval
Annotations:
Selector: app=hazelcast-enterprise,release=dining-serval,role=mancenter
Type: LoadBalancer
IP: 10.100.98.225
LoadBalancer Ingress: a539e0f709f3111e8b9d00af5b0ce326-465655592.us-west-2.elb.amazonaws.com
Port: mancenterport 8080/TCP
TargetPort: mancenter/TCP
NodePort: mancenterport 31877/TCP
Endpoints: 192.168.246.76:8080
Session Affinity: None
External Traffic Policy: Cluster
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal EnsuringLoadBalancer 6m service-controller Ensuring load balancer
Normal EnsuredLoadBalancer 6m service-controller Ensured load balancer
```

Start with the INDEX.txt deployment instructions for Management Center and compare them with the kubectl describe svc output in the issue. Update the AWS EKS guidance so users can find the LoadBalancer Ingress URL, then verify that the documented steps match the shown service details.

Written by the indexing model from the issue text.