Setting Up Your Linux Environment

Why Two Methods?

We'll explore two primary methods for creating your Linux environment:

1. Local Virtual Machine (VM): Using software like VirtualBox, you can run a complete, isolated Linux operating system inside your current Windows or macOS computer. This is a fantastic, no-cost way to experiment freely without affecting your main system.
2. Cloud Instance (AWS EC2): This involves launching a virtual server in the cloud. This method mirrors how businesses run their infrastructure and is an indispensable skill for any DevOps engineer.

Both approaches have their merits, and being familiar with both will serve you well. We'll start with the local VM, as it's self-contained and a great way to understand virtualization at a basic level.

Part 1: Setting Up a Local Virtual Machine with VirtualBox

A virtual machine is essentially a computer within a computer. We will use Oracle's VirtualBox, a free and widely-used virtualization tool, to create an Ubuntu Linux VM. Ubuntu is one of the most popular Linux distributions, especially in cloud and server environments.

The following tutorial from the official Ubuntu website provides a comprehensive, step-by-step guide. We'll use it to walk through the entire process.

Key Steps and Considerations

As you follow the tutorial, pay close attention to these steps:

1. Download and Install:

   • First, download and install VirtualBox for your operating system (Windows, macOS, etc.).
   • Next, download the Ubuntu Desktop ISO. The tutorial may reference a specific version, but it's always a good practice to use the latest LTS (Long-Term Support) version, as it offers stability and security updates for five years. You can find it on the Ubuntu download page linked in the tutorial.

2. Create the VM:

   • When creating the new VM, the "Unattended Guest OS Install" feature will save you a lot of time.
   • Crucially, change the default username and password. The tutorial warns that the default vboxuser does not have sudo (administrative) privileges, which you will absolutely need. Choose a username and a memorable password for yourself.
   • Allocate Resources: The guide suggests around 8GB of RAM and 4 CPUs for good performance. If your host machine has fewer resources, 4GB of RAM and 2 CPUs are a workable minimum. A 25GB hard disk is a good starting point.

3. First Boot and Updates:

   • After the installation finishes and your new Ubuntu Desktop boots up, the first thing you should always do is update the system's package list and upgrade the installed software. This is a fundamental system administration task.
   • Open the Terminal application in Ubuntu (you can find it by searching) and run the following command:

     sudo apt update && sudo apt upgrade -y
     

   • You will be prompted for the password you created during setup. Note that you won't see characters appear as you type your password; this is a security feature in Linux.

You now have a fully functional Linux desktop running on your machine, ready for you to explore!

Part 2: Launching a Cloud Instance with AWS EC2

While a local VM is great for learning, most real-world DevOps work is done on cloud infrastructure. Amazon Web Services (AWS) is the dominant cloud provider, and its Elastic Compute Cloud (EC2) service is used to run virtual servers, which AWS calls "instances."

For this part, you will need an AWS account. If you don't have one, you can sign up on the AWS website. New accounts are eligible for the AWS Free Tier, which provides a certain amount of resource usage for free for 12 months. We will stick to Free Tier resources to avoid any costs.

The official AWS "Get Started" guide is the best resource for this.

Key Steps and Concepts

As you follow the AWS tutorial, focus on understanding these core ideas:

1. Amazon Machine Image (AMI): This is a template that contains the operating system and software for your instance. For our purposes, select the Ubuntu Server LTS AMI that is marked "Free tier eligible."

*This is the screen in the AWS console where you select the operating system (AMI) for your new EC2 instance. Notice the 'Free tier eligible' tags, which are important to select to avoid costs.*

2. Instance Type: This defines the hardware resources (CPU, RAM) for your instance. The t2.micro instance type is typically included in the Free Tier and is sufficient for our learning needs.

3. Key Pair: This is a set of cryptographic keys used to prove your identity when connecting to the instance. You will create a key pair, and AWS will provide you with a private key file (a .pem file) to download. Guard this file carefully; you cannot download it again.

4. Security Group: This acts as a virtual firewall for your instance, controlling inbound and outbound traffic. The default settings will create a rule to allow SSH traffic from any IP address (0.0.0.0/0). This is fine for our short-term learning but is not secure for production environments.

5. Connecting with SSH: After your instance is running, you'll connect to it using Secure Shell (SSH). This is the standard command-line protocol for managing remote servers. The tutorial provides the exact ssh command to use, which will look something like this:

   ssh -i /path/to/your-key-file.pem ubuntu@public_dns_of_your_instance
   

   You'll run this command from the terminal on your own computer (e.g., Terminal on macOS/Linux or PowerShell/WSL on Windows).

6. Cleaning Up: This is the most critical step. Cloud resources cost money. The Free Tier is generous, but once you are finished with an instance, you must terminate it to stop incurring charges. The tutorial's "Step 3: Clean up your instance" shows you exactly how to do this.

Conclusion and Next Steps

Congratulations on completing this foundational lesson! You now have the practical skills to create your own Linux practice environment, which is the launchpad for everything else in this course.

Key Takeaways:

• A local virtual machine (using VirtualBox) is a free, isolated environment running on your own computer, ideal for safe experimentation.
• A cloud instance (like AWS EC2) is a virtual server running in a provider's data center, which mirrors how modern applications are deployed in the real world.
• The setup process for a VM involves installing virtualization software, obtaining an OS image (ISO), and configuring the virtual hardware.
• The setup process for an EC2 instance involves selecting an image (AMI), instance type, and configuring security (key pairs, security groups) through a web console.
• Always remember to terminate cloud resources when you are done with them to avoid unexpected costs.

For the upcoming lessons in this module, either environment will work perfectly. I recommend using the VirtualBox VM you created as your primary environment for now. It's simple, always available, and carries no risk of cost.

In our next lesson, we will boot up your new Linux system and take our first steps inside it. You'll learn how to navigate the Linux file system using absolute and relative paths, a fundamental skill for working on any Linux machine.