My Journey to Setting Up an EC2 Instance
To build an EC2 instance, I followed these steps:
I am currently taking a course on the foundations of the cloud, and one of our first assignments was to build an EC2 instance using an Apache2 server on Ubuntu.
This was a great opportunity for me to learn more about cloud computing and how to set up a web server.
Here are the steps I followed:
Go to the AWS Management Console and select the EC2 service.
In the Launch Instance wizard, select the Ubuntu Server 20.04 LTS AMI.
For the instance type, select a free tier instance, such as the t2.micro.
For the VPC(Virtual Private Cloud), select the default VPC.
For the subnet, select a subnet desired region.
For the storage, select the default EBS (Elastic Block Storage) volume of 8 GiB.
In the Tags section, add a tag with the name Name and the value MyEC2Instance.
In the Security Groups section, select the default security group.
Review the configuration and click Launch.
Once the instance is launched, it will take a few minutes to boot up. When it is ready, you can connect to it using SSH (Secure Shell). Which leads me to my point about terminology.
It's so confusing and unnecessary. Why can't we just call things what they are?
For example, why do we have to call a virtual computer an "instance"? Why can't we just call it a "computer"? An EC2 instance is a virtual computer that runs on Amazon Web Services (AWS).
And why do we have to call an operating system an "OS"? Why can't we just call it an "operating system"?
Tech terminology is just so pretentious. It makes people who don't know anything about tech feel like they're stupid.
So, if you're a tech person, please stop using tech terminology. It's not helping anyone.
Just talk to us like we're human beings.
If you want to learn more about the origin of the internet and how Silicon Valley has made it so confusing, listen to this podcast:
Once you understand the origin then you have context and then you realize its not that complicated.