Thanks Namit. The host ip is pingable from the ssh terminal. I was able to do ssh as well. But tried the secure and unsecure UI links as suggested but am getting the same error as below. When Google Chrome tried to connect to (Address) this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be (Address). or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged. You cannot visit ec2-34-206-146-156.compute-1.amazonaws.com right now because the website sent scrambled credentials that Google Chrome cannot process. Network errors and attacks are usually temporary, so this page will probably work later. I have compared the securiy in bound settings with the controller for the master and data nodes, which are all same. Any thing I am missing? ... View more

Thank you Sunile. Is the public dns the one in AWS relevant to the ip address ? If yes, I have tried it but the I am getting the below error which was same as the previous. When Google Chrome tried to connect to (Address) this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be (Address). or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged. You cannot visit ec2-34-206-146-156.compute-1.amazonaws.com right now because the website sent scrambled credentials that Google Chrome cannot process. Network errors and attacks are usually temporary, so this page will probably work later. I have compared the securiy in bound settings with the controller for the master and data nodes, which are all same. Any thing I am missing? ... View more