By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

AWS Transfer Authentication Failure

0

I created a SFTP server in AWS Transfer family connected to an S3 bucket with the service managing the users. Created 3 users and it was all working fine. I created a fourth user (with the same IAM role attached as the working users) and it did not work and received an SSH AUTH FAILURE when trying to connect. So I added the public key to the user again (assuming I had screwed up). The two keys both show the same fingerprint in the AWS transfer console so I didn't screw up. But still does not work. However, when I checked the fingerprint of the key locally using 'ssh-keygen -l -f <keyname>' I get a totally different fingerprint to the one shown against the keys for that user.

So I removed the key from one of the working users and added the exact same public key back in. That user no longer works but the public key has not changed.

What am I doing wrong here?

Topics
Security, Identity, & ComplianceMigration & Modernization
Tags
AWS Identity and Access ManagementAWS Transfer Family
Language
English
AWS-User-0962411
asked 2 years ago1018 views
1 Answer
0

I found out why the keys were causing a problem and it turned out to be a copy and paste error. I was opening the public key file in an editor, selecting all, doing a copy and then pasting into the web console. If is use the command line tool xclip to copy the contents of the file and paste that into the web console the keys work fine.

I knew I was doing something stupid.

AWS-User-0962411
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content