Through this Article, I am going to explain the steps required to create the Virtual Machine with EC2 from AWS (Amazon Webservice) Management Console. Assuming you have the account to use AWS Management Console.
Step 1. Log in into “AWS Management Console”.
Step 2. Under Build Solution group, click on “Launch a virtual machine” link. AWS will open a wizard to allow us to create a Virtual Machine instance (EC2 instance).
Step 3. Choose an Amazon Machine Image (AMI) contains the software configuration required to launch the EC2 instance. Select the AMI which is suitable for your need by clicking on the Select button next to the displayed AMI template. Once selected, the Console will take us to next step to select an instance from “Choose an Instance Type” wizard page.
Note: By clicking “Free tier only” checkbox, will display the AMIs which are qualified for Free tier.
Step 4. Select the instance type which suits our requirement, and click on “Next: Configure Instance Details” to go to next wizard step.
Note: Free tier eligible entries will be shown in the list, with “Free tier eligible” text under the entries in Type column.
Step 5.“Configure Instance Details” allows to configure the instance to suit your requirements. Keep the default values, if you do not want to modify anything.
Give number of instances value in “Number of instances” field; to launch the number of instances from the same selected AMI.
You can assign the access management role to the Instance through “IAM role” field.
Once the necessary values are entered, click on “Next: Add Storage” button to add the storage to the instance(s).
Step 6.“Add Storage” wizard page, allows you to update the storage device settings. You can also add new volumes depends on your requirements. Once the values are given, click on “Next: Add Tags” button.
Step 7. After adding the Tags, click on “Next: Configure Security Group” button.
Step 8. “Configure Security Group” wizard allows to add rules to control the traffic for EC2 instance. For example: you can add rules to allow to access the EC2 instance from known IP addresses only. Once required changes are done, click on “Review and Launch” button.
Step 9. Before launching the instance, AWS Management Console will prompt a message, to create a key pair entry to attach to the instance. You can create a new key pair or you can use the already created one. This key pair is important to connect to the EC2 instance. Key pair contains both public & private keys. You need to download the Key Pair and store it in a secured location from where you can access whenever you want to connect to EC2 instance.
Provide the “Key pair name” & click on Download Key Pair button to download the key pair file (*.pem file). Once downloaded, click on Launch Instances button to launch the EC2 instances.
Step 10. If everything goes fine, you will see “Your instances are now launching” message. And you can also review the settings you have done. Click on “View Instances” button to view the instances which we created just now through the above steps.
Step 11. You can see the list of instances and their statuses on the instances page. Now EC2 instance is ready, that means, your own virtual machine is ready. Everything is ready; then how to connect to it.?
Step 12. Click on Connect button, which is on top of the EC2 instances page. AWS Management Console will display the steps to connect to the EC2 instances. You can connect to EC2 instances, using SSH client or through web-browser.
I will explain the steps on connecting to EC2 instance using SSH client, in my next Article.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.