Difference between revisions of "AWS"

From Ever changing code
Jump to navigation Jump to search
Line 15: Line 15:


=== EC2 Security Group ===
=== 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:
Remember to assign 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:
[[File:Ec2-security-group.png|none|600px|thumb|left|Ec2-security-group]]
[[File:Ec2-security-group.png|none|600px|thumb|left|Ec2-security-group]]

Revision as of 12:29, 18 August 2013

ssh to EC2 instance

SSH theory using a private and public key

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 assign 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:

Ec2-security-group