| Author |
Topic: Absolutely first step to set up AWS |
|
Linux
member
offline  |
| |
| posts: |
120 |
| joined: |
01/24/2011 |
| from: |
San Jose, CA |
|
|
 |
|
|
| Absolutely first step to set up AWS |
Just follow the instructions as detailed in the blog, it is working.
http://whatiscomingtomyhead.wordpress.com/2010/11/24/absolute-first-step-tutorial-for-amazon-web-services/
After the link, you should have now a running AWS EC2 instance which is a Linux box
|
|
|
|
|
|
|
Linux
member
offline  |
| |
| posts: |
120 |
| joined: |
01/24/2011 |
| from: |
San Jose, CA |
|
|
|
|
|
| SSH connection to AWS instance |
Once your instance is running in the cloud, you may want to manage it.
On Unix/Linux, just ssh to it.
On Windows, you may want to use WinSCP/Putty to do that. Here is a good link to detail the process. Make sure to log on as ec2-user not root.
http://www.keywordintellect.com/amazon-web-services/managing-an-amazon-ec2-instance-using-putty-ssh/
After login, type the command:
# sudo su
You are now swithed to root
|
|
|
|
|
|
|
Linux
member
offline |
| |
| posts: |
120 |
| joined: |
01/24/2011 |
| from: |
San Jose, CA |
|
|
|
|
|
| Create a new EC2 instance |
Step 1). Open the AWS Management Console and select the EC2 (Virtual Server in Cloud). Select your desired region (US West) to launch the instance and afterwards click on launch instance.
Step 2). Select Classic Wizard to continue.
Step 3). Select Amazon Linux AMI 2012.03 (64-bit) to continue.
Step 4). Take defaults on the next two screens (Intance Type: Micro (t1.micro 613MB)) and skip the adding Tags page.
Step 5). Create a new Key Pair with a key name (myEC2Key) and download the private key file: myEXC2Key.pem.
Step 6). Setup your firewall rules:
Inbound Rules: SSH 22 HTTP 80 HTTS 443
Step 7). After clicking on Launch, your instance should be running in the cloud.
|
|
|
|
|
|
|
Linux
member
offline |
| |
| posts: |
120 |
| joined: |
01/24/2011 |
| from: |
San Jose, CA |
|
|
|
|
|
| Manage your AWS EC2 instance via Public DNS host name |
Step 1) Download WinSCP.
Step 2) Convert AWS's key (.pem) into PuTTY format (.ppk):
Run <WinSCP>/PuTTY/puttygen.exe;
Click Load from the main screen and select the key that we saved when we were creating our Amazon EC2 instance;
Once the key is loaded, click on Save Private Key button;
You will get a warning about saving the key without a passphrase. Click Yes to generate a PuTTY format key.
Step 3) Run <WinSCP>/WinSCP.exe
Click on New button;
Host name: ec2-xxx-xxx-xxx-xx.us-west-1.compute.amazonaws.com
User name: ec2-user
Private key file: xxx.ppk converted from step 2.
Save the profile and Login.
Now you are on WinSCP window.
Step 4) Open PuTTY session
Click on PuTTY icon;
You are on /home/ec2-user and connected as ec2-user
$ sudo su
Now you are connected as root
# exit
Now you are exited and connected as ec2-user
$ exit
Now you are out.
|
|
|
|
|
|
|
Linux
member
offline |
| |
| posts: |
120 |
| joined: |
01/24/2011 |
| from: |
San Jose, CA |
|
|
|
|
|
| Access your AWS EC2 instance via Elastic IP Address |
Step 1) Log into your AWS EC2 Management Console;
Step 2) Click on Elastic IPs under NETWORK & SECURITY;
Step 3) Launch Allocate Elastic IP Request;
Step 4) on Elastic IPs Address panel, click on Associate Address
Step 5) Select an instance and click on Yes
Now your AWS EC2 instance has been associated with an IP Address: xxx.xxx.xxx.xxx
Note: After association, your instance's Public DNS may change accordingly with the newly created IP Address replacing the temporarily assigned one.
|
|
|
|
|
|
|
Email To Friend | 
Set Alert To This Topic
New Topic | 
Post Reply 
posted on: 10/12/2011 06:11:44 PM
Edit
Quote
Report
Profile
Reply