- \n
- Choose an AMI<\/li>\n
- Choose an instance type<\/li>\n
- Configure instance<\/li>\n
- Add storage<\/li>\n
- Add tags<\/li>\n
- Configure Security group<\/li>\n
- Review<\/li>\n
- Generate key pair<\/li>\n<\/ul>\n<\/div>\n
Choose an AMI<\/h2>\n
Amazon give the acronym AMI to represent all of the machine images that you can choose.\u00a0 Of course Amazon has their own Linux distribution but they also have a lot of other popular distributions available as well.<\/p>\n
\n- \n
- Redhat<\/li>\n
- SUSE<\/li>\n
- Ubuntu<\/li>\n
- Windows 2016 server<\/li>\n<\/ul>\n<\/div>\n
You can select whichever distribution you feel the most comfortable with.<\/p>\n
![\"\"](\"https:\/\/blog.paranoidprofessor.com\/wp-content\/uploads\/2017\/11\/aws-01-ec2-launch-select-ami.png\")
<\/p>\n<\/p>\n
Choose an instance type<\/h2>\n
The next step is to select the resources that should be made available to the machine.\u00a0 The resources is all the same as for a physical computer.\u00a0 This is the number of cpu’s, or virtual cpu’s, the memory and disk space.\u00a0 I have chosen a small machine for testing.<\/p>\n
![\"\"](\"https:\/\/blog.paranoidprofessor.com\/wp-content\/uploads\/2017\/11\/aws-02-ec2-launch-select-ami.png\")
<\/p>\n<\/p>\n
Configure instance<\/h2>\n
The next step is to select your vpc and which subnet (assuming more than one exists).\u00a0 Assuming you correctly did all of your steps correctly in creating it your virtual machine will get a public IP.<\/p>\n
![\"\"](\"https:\/\/blog.paranoidprofessor.com\/wp-content\/uploads\/2017\/11\/aws-03-ec2-launch-select-configure.png\")
<\/p>\n<\/p>\n
Add storage<\/h2>\n
Your EC2 will already have a drive assigned to it.\u00a0 This is also were you could add additional volumes.\u00a0 I haven’t actually needed any permanent storage for my tests so I left the default for this, however, in the future I will write up an example adding additional storage.<\/p>\n
![\"\"](\"https:\/\/blog.paranoidprofessor.com\/wp-content\/uploads\/2017\/11\/aws-04-ec2-launch-add-storage.png\")
<\/p>\n<\/p>\n
Add tags<\/h2>\n
This is a totally optional step.\u00a0 You can create a number of tags that will be displayed with your machine.\u00a0 I believe that these tags will also be on your billing statement.<\/p>\n
![\"\"](\"https:\/\/blog.paranoidprofessor.com\/wp-content\/uploads\/2017\/11\/aws-05-ec2-launch-add-tags.png\")
<\/p>\n<\/p>\n
Configure Security group<\/h2>\n
At this point it is either possible to create a new security group or select the one that was created while creating your VPC.<\/p>\n
![\"\"](\"https:\/\/blog.paranoidprofessor.com\/wp-content\/uploads\/2017\/11\/aws-06-ec2-launch-security-group.png\")
<\/p>\n<\/p>\n
Review<\/h2>\n
With these few steps done Amazon gives you a chance to review all of your settings before actually committing to this EC2 instance.<\/p>\n
![\"\"](\"https:\/\/blog.paranoidprofessor.com\/wp-content\/uploads\/2017\/11\/aws-07-ec2-launch-review.png\")
<\/p>\n<\/h2>\n
Generate key pair<\/h2>\n
Oddly enough I would have thought that this step would have been before the review.\u00a0 The only way to connect to your machine is with a public \/ private key pair.<\/p>\n
This will be the only opportunity to download the key pair so you should save it in a good location.\u00a0 While creating other EC2 instances it is possible to either create another new pair or use an existing key pair.<\/p>\n
![\"\"](\"https:\/\/blog.paranoidprofessor.com\/wp-content\/uploads\/2017\/11\/aws-08-ec2-launch-keypair.png\")
<\/p>\nAt this point when you press the “Launch Instances” button the EC2 instance is created.<\/p>\n
![\"\"](\"https:\/\/blog.paranoidprofessor.com\/wp-content\/uploads\/2017\/11\/aws-09-ec2-launch-launched-status.png\")
<\/p>\nPressing the instances button will bring up the dashboard.<\/p>\n
<\/p>\n
Dashboard<\/h2>\n
The dashboard will show all of the running, stopped or terminated instances.\u00a0 The terminated instances will be displayed for a short period of time and then eventually will be removed.<\/p>\n
![\"\"](\"https:\/\/blog.paranoidprofessor.com\/wp-content\/uploads\/2017\/11\/aws-10-ec2-launch-dashboard.png\")
<\/p>\nSummary<\/h2>\n
Once your instance shows up on the dashboard as running you can then connect to it.\u00a0 Simply ssh to your virtual machine using your private key.\u00a0 In this example the machine name is rather a mouthful.<\/p>\n
ec2-13-59-244-104-us-east-2.compute.amazonaws.com<\/p>\n
However, Amazon does make it easy to connect to your machine, well, if you happen to be using linux or unix.\u00a0 Simply select your machine and choose “connect” from the actions button at the top of the screen.\u00a0 This will bring up a dialog showing the actual command that you need to use to connect to the machine.<\/p>\n
ssh -i\u00a0 \"apacheAMI.pem\" root@ec2-13-59-244-104-us-east-2.compute.amazonaws.com<\/pre>\n
If you are not actually using some flavor of unix you will need to do a few other small changes in order to connect to your machine, but Amazon is good enough to have a web page that documents this process<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
Elastic compute cloud A EC2 – an elastic compute cloud – is just a simple virtual machine.\u00a0 Amazon does have a lot of really interesting ways of using virtual machines to solve problems.\u00a0 The first step is to create an … Continue reading