AlanM's picture

I deployed the File Server instance in AWS EC2 and created security group rules that are limited to just my subnet so that SSH wasn't exposed to the internet.  I have the key pair, but every time I try to SSH in to start the config it refuses the login with "Too many authentication failures".

Any tips on how to get access to it or suggestions for what is failing?

AlanM's picture

I think I figured it out.  I turned on verbose with my ssh client and saw that it was trying some of the other keys that I had loaded in the agent before trying the one I specified with the "-i" option and failing before it got to the correct private key.

Jeremy Davis's picture

I'm glad to hear that you got it sorted! :)

FWIW in an effort to mitigate the risks of having SSH exposed to the world, we have hardened the default config for SSH, plus we include and enable fail2ban (which blocks connection from your IP after too many failed attempts).

It sounds like you've got it sorted now, but if you wanted to soften some of the SSH defaults again, I can assist with that if you want (locking SSH to your subnet should provide adequate SSH security).

Good luck with it all and please do not hesitate to get in touch again if you have any further questions.

Add new comment