ssh to private ec2 via bastion using ssh-run

Question

Hello, I am trying to login into my private ec2 host via bastion host and execute a shell script in the host using following pipeline. - pipe: "atlassian/ssh-run:0.4.1" variables: SSH_USER: 'ec2-user' SERVER: $SERVER SSH_KEY: $SSH_KEY MODE: script COMMAND: bitbucket-pipelines.sh EXTRA_ARGS: -o ProxyCommand='ssh -i /root/.ssh/pipelines_id ec2-user@16.210.69.43 -W %h:%p' But I always get below error : Bad stdio forwarding specification '%h:%p'' Output: INFO: Executing the pipe... INFO: Using passed SSH_KEY INFO: Executing script bitbucket-pipelines.sh on 10.9.181.1 ssh -i /root/.ssh/pipelines_id -o StrictHostKeyChecking=no -p 22 -o ProxyCommand='ssh -i /root/.ssh/pipelines_id ec2-user@16.210.69.43 -W %h:%p' ec2-user@10.0.141.68 bash -s Bad stdio forwarding specification '%h:%p'' ✖ Execution failed.Status: Downloaded newer image for bitbucketpipelines/ssh-run:0.4.1 Can someone please help me with this ?

Vu Ha_ibdhax · Answer

@Sukoon for ssh-run just use JumpHost instead ProxyCommand

EXTRA_ARGS: -J $SSH_USER@$BASTION_HOST for rsync-deploy use ProxyCommandSSH_ARGS: '-v -o StrictHostKeyChecking=no -o ProxyCommand="ssh -W %h:%p -q $SSH_USER@$BASTION_HOST" -l $SSH_USER'

lissyaka · Answer

@Sukoon  hi.

This problem relates to quoting.

For complex command escaping/quotas issue could happened, because pipelines infra also do some additional escaping for all passed variables to pass them throughout a docker infra.

We will investigate your issue and notify you.

Cheers.