When I try to connect to an ec2 instance with the route 53 service I bought the SSH connection disappears for no reason that I can determine.
The web server created on it works, but the ssh no longer connects or switches to the public key. I'm not even sure the DNS or path to the IP is valid.
All the forums state similar problems but the only advice is to scrap the instances and start over. Of course, that isn't an option if I wanted to develop on the server.
As far as I can tell the SSH or "connect" breaks as soon as I assign an elasticIP, and doesn't reform on the canceling of the elasticIP.
Of course, I bought the Route 53 service with the idea I could start developing and production right away, but as it turns out, I've yet to have a login. What's Amazon doing to fix the problem? Is there some esoteric step? as I can hardly conceive no one's ever used a Route53 in conjunction with the ec2.
It all works perfectly until I assign the ElasticIP, I can log in securely, update, program, whatever. After I assign the AWS EC2 instance an IP the SSH breaks, even before I assign the Route 53.