How do configure Coda to work for my Amazon EC2 instance?

I can not c开发者_开发知识库onnect to my EC2 instane. I have opened port 21 in the AWS Console. I think there is no way of input my SSH Key pair in Coda. Is there a way of connecting Coda to my EC2 instance?

---

Coda should pick up settings from your ssh config so you can configure this fairly easily.

If you've saved your EC2 ssh keypair in ~/.ssh/ec2_rsa then simply edit ~/.ssh/config to look like:

IdentityFile ~/.ssh/ec2_rsa

You can also restrict the IdentityFile directive to just your AWS resource with:

Host somehost.amazonaws.com
    IdentityFile ~/.ssh/ec2_rsa

If everything's configured properly then you should be able to, from the command line, run ssh username@awshost and get a login prompt

If you continue to have problems you can always enable password authentication on your instance by editing /etc/ssh/sshd_config and adding the line PasswordAuthentication yes to the end of the file, then setting a password for your user with passwd

I use the following settings in my .ssh/config to automatically apply my EC2 keypairs for EC2 resources:

# EC2 Northern Virginia
Host *.compute-1.amazonaws.com
    IdentityFile ~/.keys/ssh/ec2/us_east_1.key
    StrictHostKeyChecking no
    UserKnownHostsFile /dev/null
    IdentitiesOnly yes
    ForwardAgent no

# EC2 Northern California:
Host *.us-west-1.compute.amazonaws.com
    IdentityFile ~/.keys/ssh/ec2/us_west_1.key
    StrictHostKeyChecking no
    UserKnownHostsFile /dev/null
    IdentitiesOnly yes
    ForwardAgent no

# EC2 Ireland:
Host *.eu-west-1.compute.amazonaws.com
    IdentityFile ~/.keys/ssh/ec2/eu_west_1.key
    StrictHostKeyChecking no
    UserKnownHostsFile /dev/null
    IdentitiesOnly yes
    ForwardAgent no

# EC2 Singapore:
Host *.ap-southeast-1.compute.amazonaws.com
    IdentityFile ~/.keys/ssh/ec2/ap_southeast_1.key
    StrictHostKeyChecking no
    UserKnownHostsFile /dev/null
    IdentitiesOnly yes
    ForwardAgent no

# EC2 Tokyo:
Host *.ap-northeast-1.compute.amazonaws.com
    IdentityFile ~/.keys/ssh/ec2/ap_northeast_1.key
    StrictHostKeyChecking no
    UserKnownHostsFile /dev/null
    IdentitiesOnly yes
    ForwardAgent no

---

I struggled with this for some time, so sharing important steps for me:

1. Configure an alias in /.ssh/config
2. Make sure permissions of my_key.pem makes sense, eg. do > chmod 644 my_key.pem
3. Simply put your alias in Server field when creating SSH or SFTP session, and nothing else.

That worked for me.

---

In the new version of Coda, there's a small icon of a key which shows up inside the password box on the right. If you click this, you can browse to the PEM file and choose that as your password.

The icon disappears once you click the password box, and as far as I can tell you can't get it back without making a new project.