Difference between revisions of "AWS"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
*RedHat user: root (tbc) | *RedHat user: root (tbc) | ||
*Amazon branded instances: ec2-user (to be confirm) | *Amazon branded instances: ec2-user (to be confirm) | ||
Connecting and useful flags <code> -l username</code> specifies linux account user name, <code>-v</code> verbose mode | |||
ssh -i mykey.pem ubuntu@ec2-user@ec2-99-99-99-99.compute-1.amazonaws.com | ssh -i mykey.pem ubuntu@ec2-user@ec2-99-99-99-99.compute-1.amazonaws.com | ||
Revision as of 11:47, 18 August 2013
ssh to EC2 instance
Change permissions of the key to ready only by owner as per Getting Started with Amazon EC2 Linux Instances
chmod 400 mykey.pem -r------- 1 user user 1766 Aug 18 01:17 mykey.pem
- Ubuntu user: ubuntu (confirmed)
- RedHat user: root (tbc)
- Amazon branded instances: ec2-user (to be confirm)
Connecting and useful flags -l username specifies linux account user name, -v verbose mode
ssh -i mykey.pem ubuntu@ec2-user@ec2-99-99-99-99.compute-1.amazonaws.com
EC2 Security Group
Remember to assing the security group that applies to your scheme on your instance. Having port open on the instance does not mean you will be able to access from outside. It must bypass EC2 Security Group first. Overview below:
