Creating AWS EC2 instance


We are going to deal with how to access CLI of a Linux server/system. So tag along as we go through a little history as well. 

There are mainly two ways (that we are going to discuss) for accessing the terminal : 

  • Your PC/System has Linux OS such as Ubuntu, CentOS, etc.
  • Your PC/System doesn't have Linux OS but has Mac/Windows OS

Let's talk about these ways in detail:

  • You use Linux OS 

Easier option because you don't have to do anything much other than to open CLI (Command-Line Interface) and write the commands.

  • You don't have Linux but have Mac/Windows OS 

Once upon a time
Once upon a time

Olden times (not like 500 years back. Maybe 20 years? Feel old? We are.), we installed Linux in the system and do the above. But it was neither easy nor quick (It is still an option, but one in many.). So, Virtual Machines were introduced where we could run another OS as if it was running on its own independent hardware, so as to allow time-sharing among several single-tasking operating systems . This process is known as Virtualization. In detail, Virtualization is the process of taking one or more components of a computer, such as CPUs, RAM, and storage, and tricking a piece of software, here Mac/Windows OS, into thinking those components are their physical counterparts. 

The concept of virtualization has evolved with the internet, as businesses began offering “virtual” private networks as a rentable service. The use of virtual computers became popular, leading to the development of the modern cloud computing infrastructure. To sum it up, virtualization is a software that manipulates hardware, while cloud computing refers to a service that results from that manipulation. You can't have cloud computing without virtualization. It is the foundation of cloud computing where applications, servers, storage and network can all be virtualized. 


I know you are wondering "So what is the point?". The point is: You can easily use the cloud platforms (here, we will be dealing with AWS) to create an instance, which is is a virtual server/system. One can set up and configure the operating system (here, Linux) and applications (here, CLI) that run on your instance. It's just a few clicks away, quick, hassle free, secure and pay as you go option. A gist of why companies are migrating to cloud platforms (which is a discussion for another day).

How to "Create an AWS EC2 instance"?

  • Login to your AWS account (Don't forget your password!). If you are a beginner, a free tier for a year is available, sign up. There are numerous services AWS provides.
AWS Login
  • Go to EC2 --> Launch instances. You will be taken to the "Launch an instance" page for filling the details.
Go to EC2 services

Select Launch instances
  • Choose name, Ex) Example Instance; server type from AMI (Amazon Machine Image contains virtual copies of operating system, application server, and applications required to launch the instance), here, Ubuntu; key pair if already existing, otherwise create one by clicking on "Create new key pair" in type "RSA" and file format as ".ppk" and checkbox the 3 boxes in "Network Settings" for accessing the IP address in web browser. (NOTE: Only mentioning the editing options as the others remain untouched.) 
Type name of instance

Select Ubuntu

Select Keypair from dropdown if available otherwise do as below

Create keypair name, type and file format as above

Tick the 3 checkboxes
  •  Now, "Launch instance". You have successfully launched the instance.
Click Launch instance in the bottom right corner

Instance created successfully
  • Once the instance is running and the status checks are done, "Connect" to instance. Go to "EC2 instance connect". 
Click on connect to access the instance

  • A console will be launched giving you access to the CLI of Ubuntu server/system.
Loading the console

The Ubuntu console

We have come to the end of the article. This is an attempt in simplifying numerous and enormous subjects. Hence, bear with my efforts. Feel free to comment any mistakes and suggestions.

Taking your leave the traditional way.

And definitely don't forget to terminate your instances when not in use.

Toodaloo!


 



Comments

Post a Comment

Popular posts from this blog

Version Control Systems (VCS)

Image
If you are in the Software field, you've definitely heard the word "Git". Probably, the first time you've ever heard the word is along the words "Create a new branch. Don't touch the main branch". Don't go watering your office plants if you hear that (I tried to joke. Please laugh:') )! Let's see what it means. Don't touch the Master There are developers who are coding/developing/rectifying "features" for a single project (a website or a software or application. An end product). It's going to be very difficult and time consuming building a project single handedly, which is usually why, there is a team of developers. It's also going to be difficult and time consuming if everybody has to code on a single PC, taking turns. Mostly, developers of the company are also in different parts of the world, making collaboration a necessity.  So, every developer has their own PC. They are coding in their file. As they do so, various m...
Read more

Linux commands - Part II - How?

Image
The last articles dealt with how you would get to a terminal to execute Linux commands and why we have the need to execute these commands. Summing up, a terminal from an Ubuntu instance doesn't provide a GUI. Hence, we require Linux commands to interact with the system via terminal.  Fun fact: Unix and Linux are not synonymous. Linux is the clone of Unix. It has several features similar to Unix but they still have some key differences. This article should give a fair idea of the differences. Do check out if interested. (Note: I'm only including the commands I'm aware of and USED in tasks. If you are a beginner, there's no better way to understand the working other than doing them along. You only get better understanding while using them for your tasks, otherwise they are not only boring but also difficult to grasp.) Now we deal with "The" commands. We'll divide the commands according to their functionality for better understanding.  Directory commands A...
Read more

Basic Linux Commands I - Why and What?

Image
After what seemed like a huge break, I wanted to write something I currently find interesting. I was recently looking through Linux commands and basically went " OOhlala".  Never liked them during college days and only did them like under "command". I was trying to figure out why and my conclusion is as below (Yup, did an investigation and all) : Only used Linux commands during labs. They asked us to find as many commands as possible by "Googling", try it in the prompt and write it down in the book. They'd also add, to "Learn them" because "We'll be asking questions". I remember looking up the commands, trying them out and wondering what exactly this "gibberish" means and also trying to byheart them as they were about to ask questions (last minute Queen ). Well, they did us bad by blocking YouTube and also certain technical websites which would apparently "make the learning easy"??? (along with the cliché ...
Read more