Cannot connect AWS Transfer via SFTP

0

I just setup a new server on AWS Transfer. I enable SFTP and use Service managed for identity provider. I created a user with role and policy that should have access to S3 bucket I want to interact, and I added ssh public key.

Now I try to connect SFTP server following guide, but I could not connect
https://docs.aws.amazon.com/transfer/latest/userguide/getting-started-use-the-service.html#cyberduck

With Cyberduck I got "Interoperability failure" "EOF while reading packet. Please contact your web hosting service provider for assistance."
I also tried sftp command but no luck.

What can we try to trouble shoot this? cloudwatch has nothing.

Below is output form SFTP command (I replace my server name with s-xxxxx)
sftp -vvv -i ~/.ssh/awstest kazuki-test@s-16def29693e541d5a.server.transfer.us-east-1.amazonaws.com

sftp -vvv -i ~/.ssh/awstest kazuki-test@s-xxxxx.server.transfer.us-east-1.amazonaws.com
OpenSSH_7.5p1, OpenSSL 1.0.2s 28 May 2019
debug1: Reading configuration data /Users/kazuki/.ssh/config
debug1: /Users/kazuki/.ssh/config line 3: Applying options for *
debug1: /Users/kazuki/.ssh/config line 66: Applying options for *
debug2: checking match for 'exec "/usr/local/bin/step ssh check-host %h"' host s-xxxxx.server.transfer.us-east-1.amazonaws.com originally s-xxxxx.server.transfer.us-east-1.amazonaws.com
debug1: Executing command: '/usr/local/bin/step ssh check-host s-xxxxx.server.transfer.us-east-1.amazonaws.com'
debug1: permanently_drop_suid: 502
debug3: command returned status 1
debug3: /Users/kazuki/.ssh/config line 67: not matched 'exec "/usr/local/bin/step ssh check-host s-xxxxx.server.transfer.us-east-1.amazonaws.com"'
debug2: match not found
debug1: Reading configuration data /usr/local/etc/ssh/ssh_config
debug1: auto-mux: Trying existing master
debug1: Control socket "/Users/kazuki/.ssh/sockets/98b42242aeb5403d857ec57a3a002a3dcef0f0b1" does not exist
debug2: resolving "s-xxxxx.server.transfer.us-east-1.amazonaws.com" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to s-xxxxx.server.transfer.us-east-1.amazonaws.com [3.217.63.140] port 22.
debug1: Connection established.
debug1: identity file /Users/kazuki/.ssh/awstest type 1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/kazuki/.ssh/awstest-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.5
debug1: Remote protocol version 2.0, remote software version AWS_SFTP_1.0
debug1: no match: AWS_SFTP_1.0
debug2: fd 6 setting O_NONBLOCK
debug1: Authenticating to s-xxxxx.server.transfer.us-east-1.amazonaws.com:22 as 'kazuki-test'
debug3: hostkeys_foreach: reading file "/Users/kazuki/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /Users/kazuki/.ssh/known_hosts:342
debug3: load_hostkeys: loaded 1 keys from s-xxxxx.server.transfer.us-east-1.amazonaws.com
debug3: order_hostkeyalgs: prefer hostkeyalgs: ssh-rsa-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c
debug2: host key algorithms: ssh-rsa-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1
debug2: host key algorithms: ssh-rsa,rsa-sha2-512,rsa-sha2-256
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com
debug2: compression stoc: none,zlib@openssh.com
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: rsa-sha2-512
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
_debug1: Server host key: ssh-rsa SHA256:fbLuv_TqVBVQXVq15Ty7e/uVMpUqi5xK4z/9upU4LlQ+
debug3: hostkeys_foreach: reading file "/Users/kazuki/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /Users/kazuki/.ssh/known_hosts:342
debug3: load_hostkeys: loaded 1 keys from s-xxxxx.server.transfer.us-east-1.amazonaws.com
debug3: hostkeys_foreach: reading file "/Users/kazuki/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /Users/kazuki/.ssh/known_hosts:345
debug3: load_hostkeys: loaded 1 keys from 3.217.63.140
debug1: Host 's-xxxxx.server.transfer.us-east-1.amazonaws.com' is known and matches the RSA host key.
debug1: Found key in /Users/kazuki/.ssh/known_hosts:342
debug3: send packet: type 21
debug2: set_newkeys: mode 1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: SSH2_MSG_NEWKEYS received
debug2: set_newkeys: mode 0
debug1: rekey after 134217728 blocks
debug2: key: /Users/kazuki/.ssh/awstest (0x7ffd49d01580), explicit
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /Users/kazuki/.ssh/awstest
debug3: send_pubkey_test
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 60
debug1: Server accepts key: pkalg rsa-sha2-512 blen 279
_debug2: input_userauth_pk_ok: fp SHA256:fViont1oUaqlW/BSI9KXgkC43OuFg_BL3uMFxppvsJw+
_debug3: sign_and_send_pubkey: RSA SHA256:fViont1oUaqlW/BSI9KXgkC43OuFg_BL3uMFxppvsJw+
debug3: send packet: type 50
debug3: receive packet: type 52
debug1: Authentication succeeded (publickey).
Authenticated to s-xxxxx.server.transfer.us-east-1.amazonaws.com ([3.217.63.140]:22).
debug1: setting up multiplex master socket
debug3: muxserver_listen: temporary control path /Users/kazuki/.ssh/sockets/98b42242aeb5403d857ec57a3a002a3dcef0f0b1.WXBNdTY8hK0Cl18b
debug2: fd 7 setting O_NONBLOCK
debug3: fd 7 is O_NONBLOCK
debug3: fd 7 is O_NONBLOCK
debug1: channel 0: new [/Users/kazuki/.ssh/sockets/98b42242aeb5403d857ec57a3a002a3dcef0f0b1]
debug3: muxserver_listen: mux listener channel 0 fd 7
debug2: fd 6 setting TCP_NODELAY
debug3: ssh_packet_set_tos: set IP_TOS 0x08
debug1: control_persist_detach: backgrounding master process
debug2: control_persist_detach: background process is 54294
debug2: fd 7 setting O_NONBLOCK
debug1: forking to background
debug1: Entering interactive session.
debug1: pledge: id
debug2: set_control_persist_exit_time: schedule exit in 600 seconds
debug1: multiplexing control connection
debug3: fd 3 is O_NONBLOCK
debug3: fd 3 is O_NONBLOCK
debug1: channel 1: new [mux-control]
debug3: channel_post_mux_listener: new mux channel 1 fd 3
debug3: mux_master_read_cb: channel 1: hello sent
debug2: set_control_persist_exit_time: cancel scheduled exit
debug3: mux_master_read_cb: channel 1 packet type 0x00000001 len 4
debug2: process_mux_master_hello: channel 1 slave version 4
debug2: mux_client_hello_exchange: master version 4
debug3: mux_client_forwards: request forwardings: 0 local, 0 remote
debug3: mux_client_request_session: entering
debug3: mux_client_request_alive: entering
debug3: mux_master_read_cb: channel 1 packet type 0x10000004 len 4
debug2: process_mux_alive_check: channel 1: alive check
debug3: mux_client_request_alive: done pid = 54296
debug3: mux_client_request_session: session request sent
debug3: mux_master_read_cb: channel 1 packet type 0x10000002 len 54
debug2: process_mux_new_session: channel 1: request tty 0, X 0, agent 0, subsys 1, term "xterm-256color", cmd "sftp", env 0
debug3: process_mux_new_session: got fds stdin 8, stdout 9, stderr 10
debug2: fd 8 setting O_NONBLOCK
debug3: fd 9 is O_NONBLOCK
debug1: channel 2: new [client-session]
debug2: process_mux_new_session: channel_new: 2 linked to control channel 1
debug2: channel 2: send open
debug3: send packet: type 90
debug3: receive packet: type 80
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
debug3: receive packet: type 4
debug1: Remote: SFTP: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding
debug3: receive packet: type 4
debug1: Remote: SFTP: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding
debug3: receive packet: type 91
debug2: callback start
debug2: client_session2_setup: id 2
debug1: Sending subsystem: sftp
debug2: channel 2: request subsystem confirm 1
debug3: send packet: type 98
debug3: mux_session_confirm: sending success reply
debug2: callback done
debug2: channel 2: open confirm rwindow 0 rmax 32768
debug1: mux_client_request_session: master session id: 2
debug2: channel 2: rcvd adjust 2097152
debug3: receive packet: type 99
debug2: channel_input_status_confirm: type 99 id 2
debug2: subsystem request accepted on channel 2
debug3: receive packet: type 96
debug2: channel 2: rcvd eof
debug2: channel 2: output open -> drain
debug2: channel 2: obuf empty
debug2: channel 2: close_write
debug2: channel 2: output drain -> closed
debug3: receive packet: type 98
debug1: client_input_channel_req: channel 2 rtype exit-status reply 0
debug3: mux_exit_message: channel 2: exit message, exitval 1
debug3: receive packet: type 98
debug1: client_input_channel_req: channel 2 rtype eow@openssh.com reply 0
debug2: channel 2: rcvd eow
debug2: channel 2: close_read
debug2: channel 2: input open -> closed
debug3: receive packet: type 97
debug2: channel 2: rcvd close
debug3: channel 2: will not send data after close
debug2: channel 2: send close
debug3: send packet: type 97
debug2: channel 2: is dead
debug2: channel 2: gc: notify user
debug3: mux_master_session_cleanup_cb: entering for channel 2
debug2: channel 1: rcvd close
debug2: channel 1: output open -> drain
debug2: channel 1: close_read
debug2: channel 1: input open -> closed
debug2: channel 2: gc: user detached
debug2: channel 2: is dead
debug2: channel 2: garbage collecting
debug1: channel 2: free: client-session, nchannels 3
debug3: channel 2: status: The following connections are open:
#1 mux-control (t16 r-1 i3/0 o1/16 fd 3/3 cc -1)
#2 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cc -1)

debug2: channel 1: obuf empty
debug2: channel 1: close_write
debug2: channel 1: output drain -> closed
debug2: channel 1: is dead (local)
debug2: channel 1: gc: notify user
debug3: mux_master_control_cleanup_cb: entering for channel 1
debug2: channel 1: gc: user detached
debug2: channel 1: is dead (local)
debug2: channel 1: garbage collecting
debug1: channel 1: free: mux-control, nchannels 2
debug3: mux_client_read_packet: read header failed: Broken pipe
debug3: channel 1: status: The following connections are open:
#1 mux-control (t16 r-1 i3/0 o3/0 fd 3/3 cc -1)

debug2: set_control_persist_exit_time: schedule exit in 600 seconds
debug2: Received exit status from master 1
Connection closed

kazuki
asked 4 years ago2699 views
3 Answers
0

Please ensure your logging role is assumable by the service. transfer.amazonaws.com You can read more about creating a logging role in the Create an IAM role and policy documentation.
https://docs.aws.amazon.com/transfer/latest/userguide/requirements-roles.html

AWS
Kevin
answered 4 years ago
0

Thanks for response, I believe logging role is admin IAM that has

{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "",
"Resource": "
"
}
]
}

also can you shed some light on how to troubleshoot this?

kazuki
answered 4 years ago
0

Hi kazuki,

The IAM policy you included in your previous post appears to be the Role Policy, which defines the permissions granted after AssumeRole. However, it's the role's Trust Policy that defines who can call AssumeRole in the first place. Can you confirm that your role's Trust Policy explicitly allows transfer.amazonaws.com? For example, the Trust Policy should look like this:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "Service": "transfer.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}

You can view the Trust Policy in the IAM Console, when looking at your logging role, under Trust relationships tab. Please refer to the screenshots in https://docs.aws.amazon.com/transfer/latest/userguide/requirements-roles.html for reference.

Regards,

Ian

AWS
answered 4 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