
Key in /Users/dheward/.ssh/known_hosts:17 RSA host key forġ76.34.127.170 has changed and you have requested strict checking. Users/dheward/.ssh/known_hosts to get rid of this message.

Make damn sure my explanation of your experience actually applies to your situation!.(Most desktop SSH clients seem to ask for confirmation just like on first commit in this case by default). Now, since you are connecting to an entirely different server then the one for which the RSA key had been stored in the first place (every started EC2 instance has a respectively unique identity), your SSH client cries foul and presents the properly escalated warning you are seeing.įurthermore, it seems to disallow SSH access entirely in this situation, since you have requested strict checking. 176.34.127.170) while not encountered every day, this is all but unlikely over time given the limited number of IPv4 addresses available in general and the respective pool available for Amazon in particular. You might have gone through steps 1-4 once for another SSH server on EC2, which happened to have the very same IP address from their pool (i.e. if you don't know a reason for the change, your connection security is at risk this means, if it suddenly changed ( especially for a host you had been connecting to already without such a warning), you should indeed back out immediately and assess the situation first, i.e.on every subsequent connect to the same SSH server, your SSH client will compare the stored RSA key with the one provided by the SSH server and will present a big fat warning regarding potential nastiness if it changes, because it usually shouldn't indeed (I'll skip the rare exceptions for now).
#Bitnami wordpress stack auto starting how to
Scott Moser has distilled a great summary how to actually Verify SSH Keys on EC2 Instances and provides instructions on how to update your known_hosts file in turn as well.Furthermore, Eric discussed this topic in great detail in ssh host key paranoia.For optimal security, you are supposed to request the instance console output and find the ssh host key fingerprint in the log to verify that it is the same as the fingerprint presented to you by the ssh command. Eric's post mentions options to deal with this in principle already, i.e.ideally you'd have received this RSA key on a secure channel to properly assess its validity, however, most people simply don't do that in nowadays ever changing cloud environments, see Eric Hammond's Poll: Verifying ssh Fingerprint on EC2 Instances.your SSH client asks you to confirm this servers identity and will import the RSA key in turn for future security checks (into /Users/dheward/.ssh/known_hosts in your case).the new server presents its RSA key identity to your SSH client.


I keep getting something weird like this happen though when I run the command.ĭ-Hewards-MacBook-Pro:Downloads dheward$ ssh -i macbookpro.pem WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! I've tried the following users and commands to no avail, ubuntu, root and bitnami. It's installed and booted up fine, I've setup the security groups SSH, HTTP, HTTPs.īut weirdly enough connecting via SSH is not working, despite the front end working fine. Which is a Wordpress Multisite Bitnami Image. I've got an instance using this AMI - ami-b7a29cc3
