How do configure Coda to work for my Amazon 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.

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.

1 In Coda when you setup your site you need to use somehost.amazonaws. Com in the Server field and root in the User Name field unless you want to login as someone else and finally leave password blank. – NullRef Jun 21 at 19:52.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.