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

Problem to configure FileZilla to access my aws ec2.

0

Hi, I'm trying to configure my filezilla client to access my aws ec2 but I am having problem to connect. In my filezilla I did following definition:

  • new site: Linux aws server
  • Protocol: SFTP - SSH File Transfer Protocol (choiced)
  • Host: Public IPv4 DNS
  • Logon type: key file
  • Key File: path of my pem/ppk key
  • User: ec2-user(I don't know what I must to put in this field)
  • Ok to save my configuration. When I click to connect I receive: Status: keyfile "D:\Cezar\AWS Products\itcmedbr-keypair.ppk" Status: open Public IPv4 DNS 22 Status: Using username "ec2-user". Status: Server refused our key If I change Host from Public IPv4 DSN to Public IPv4 Address the problem is the same, for the "Server refused our key" I can't understand this key was generated in the instance proccess creation. Thanks in advance.
asked 20 days ago35 views
5 Answers
1
Accepted Answer

Hello.

For Debian, "admin" is the default username.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/managing-users.html

For a Debian AMI, the username is admin.

profile picture
EXPERT
answered 20 days ago
profile picture
EXPERT
reviewed 20 days ago
0

It seems you're encountering issues connecting to your AWS EC2 instance using FileZilla. Let's go through a few troubleshooting steps to resolve this:

  1. Username: The correct username depends on the Amazon Machine Image (AMI) you used to launch your instance. For Amazon Linux 2 or Amazon Linux AMI, the username is indeed "ec2-user". However, for Ubuntu AMIs, it's typically "ubuntu". Make sure you're using the correct username for your specific AMI.

  2. Key file format: FileZilla requires the key to be in PPK format. You mentioned you're using a .pem or .ppk file. If you're using a .pem file, you need to convert it to .ppk format using PuTTYgen:

    • Open PuTTYgen
    • Click on "Load" and select your .pem key file
    • Click on "Save private key" to save it in .ppk format
  3. Key file permissions: Ensure that your private key file has the correct permissions. On Windows, right-click the file, go to Properties, then Security, and make sure only your user account has access to it.

  4. Security Group: Verify that your EC2 instance's security group allows inbound SSH traffic (port 22) from your IP address.

  5. Instance state: Confirm that your EC2 instance is in the "running" state and has passed all status checks.

  6. Connection type: In FileZilla, try changing the "Logon type" to "Interactive" instead of "Key file" and see if that helps.

  7. Host: Using the Public IPv4 DNS is correct, but you can also try the Public IPv4 Address if the DNS doesn't work.

If you've checked all these points and are still encountering issues, you may want to try connecting via SSH using the command line to see if you get more detailed error messages. This can help identify if the problem is with FileZilla configuration or with the EC2 instance itself.

Remember, the "Server refused our key" error usually indicates an issue with the key file or permissions. Double-check that you're using the correct key pair associated with this EC2 instance and that it's properly converted to .ppk format.
Sources
Troubleshoot issues connecting to your Amazon EC2 Linux instance - Amazon Elastic Compute Cloud
Community | How to connect EC2 instance with windows OS ?

profile picture
answered 20 days ago
profile picture
EXPERT
reviewed 20 days ago
0

Ok I understood, in my case I've installed Debian OS what must type in the User field?

answered 20 days ago
0

Problem solved the user name for debian is "admin". Thanks.

answered 20 days ago
0

Thanks Riku by your assistance.

answered 20 days 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