I configured my instance. Its up and running. I can ssh in with my key (provisioned by chef/knife) before assigning an elastic IP. For example this works (before EIP):
ssh -F .ssh/config ec2-ww-xx-yy-zz.us-west1.computer.amazonaws.com
After assigning an EIP I get a:
Permission denied (publickey)
error message as its checking my home folder for the key instead of the project directory.
I even specified the config directory an the EIP:
ssh -F .ssh/config ubuntu@ww.xx.yy.zz -v
which returns a “Connection timed out message”.
When I use Elastic Fox I can see the EIP was associated correctly. Am I missing an AWS setting which denies SSH to EIPs?
Once an EC2 instance is launched, it will assign a public and private IP address. An instance’s private IP address will never change during the lifetime of that instance. However, its public dns address can change under certain circumstances.
So, after you associate an EIP to any instance, use that IP to login into your machine.