Day 01 – What is AWS? The Ultimate Guide to Amazon Web Services

Welcome to Day 1 of your 30-Day AWS Roadmap.

If you are reading this, you have decided to take a step that could fundamentally change your career. Cloud computing is not just a trend; it is the operating system of the modern internet. Whether you are a developer, a system administrator, a student, or a business leader, understanding Amazon Web Services (AWS) is no longer optional—it is essential.

In this exhaustive guide, we are not just going to skim the surface. We are going to deconstruct the cloud, travel back in time to understand why we need it, and build a foundational understanding of AWS that will serve you for the rest of your career.

Put away the other tabs. Close your textbooks. This is the only guide you need for Day 1.

The Pre-Cloud Era (Why Do We Even Need This?)

To truly understand the brilliance of AWS, you must first understand the pain of the world that existed before it. We call this the era of On-Premise Infrastructure.

The “Server Room” Nightmare

Imagine it is the year 2005. You have a brilliant idea for a startup—an online bookstore. To get this website live, you cannot just click a button. You have to become a construction company, a hardware specialist, and a security guard all at once.

Here is what your “Day 1” looked like back then:

1. Procurement: You had to order physical servers (Dell, HP, IBM). Delivery took weeks or months.
2. Space: You needed a dedicated room with specialized air conditioning because servers get incredibly hot.
3. Power: You needed industrial-grade power supplies and backup generators (UPS) in case the lights went out.
4. Networking: You had to buy routers, switches, and miles of cabling, then hire a network engineer to wire it all up.
5. Security: You needed physical locks on the doors so nobody could steal the hard drives.

The Capacity Guessing Game

The biggest problem, however, wasn’t the setup—it was the guessing.

Let’s say you bought 10 servers.

• Scenario A (Failure): Your website isn’t popular. Only 1 server is needed. The other 9 sit idle, gathering dust, wasting electricity and money. You have Over-provisioned.
• Scenario B (Success): Your website goes viral! Millions of users flood in. Your 10 servers crash under the load. You need 50 servers right now, but it takes 6 weeks to order them. Your customers leave, and your business fails. You have Under-provisioned.

This was the “Capital Expenditure” (CapEx) trap. You had to pay upfront before you made a dime.

What is Cloud Computing?

Cloud computing is the solution to the server room nightmare. But let’s look at the formal definition before we simplify it.

According to NIST (National Institute of Standards and Technology), cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services).

The Simple Definition

Think of Cloud Computing like your electric utility.

• You do not build a power plant in your backyard.
• You do not worry about how the coal is mined or the turbine spins.
• You flip a switch, and the light turns on.
• You pay only for the electricity you used at the end of the month.

Cloud Computing is the on-demand delivery of IT resources over the Internet with pay-as-you-go pricing. Instead of buying, owning, and maintaining physical data centers and servers, you access technology services, such as computing power, storage, and databases, on an as-needed basis from a cloud provider like AWS.

The 5 Pillars of Cloud Computing

If a service doesn’t have these five characteristics, it isn’t true cloud computing:

1. On-Demand Self-Service: You can provision computing capabilities (like a server) automatically without interacting with a human. No calling a sales rep. Just click and go.
2. Broad Network Access: Services are available over the network (internet) and accessed through standard mechanisms (browsers, mobile apps).
3. Resource Pooling: The provider’s computing resources are pooled to serve multiple consumers using a “multi-tenant” model. You don’t know exactly which physical box your data is on, and you don’t care.
4. Rapid Elasticity: Capabilities can be elastically provisioned and released to scale rapidly outward and inward commensurate with demand. (Scale up when busy, scale down when quiet).
5. Measured Service: Cloud systems automatically control and optimize resource use by leveraging a metering capability. You get a bill for exactly what you used.

The 3 Service Models (IaaS, PaaS, SaaS)

Not all cloud is created equal. Depending on how much control you want versus how much convenience you need, cloud computing falls into three buckets.

1. Infrastructure as a Service (IaaS)

• Definition: The most flexible category. It provides you with the basic building blocks for cloud IT. It typically provides access to networking features, computers (virtual or on dedicated hardware), and data storage space.
• Analogy: This is like renting a car. You drive it, you fill it with gas, you choose the route, you play your own music. But you don’t fix the engine or change the tires; the rental company (AWS) does that.
• AWS Example: Amazon EC2 (Elastic Compute Cloud). You get a virtual server; you choose the Operating System (Linux/Windows), and you manage the software installed on it.
• Best For: Admins who want full control over their software stack.

2. Platform as a Service (PaaS)

• Definition: Removes the need for your organization to manage the underlying infrastructure (usually hardware and operating systems) and allows you to focus on the deployment and management of your applications.
• Analogy: This is like taking a Taxi or Uber. You tell the driver where to go (your code), but you don’t drive, you don’t buy gas, and you don’t care what brand the car is.
• AWS Example: AWS Elastic Beanstalk. You just upload your code (Python, Java, etc.), and AWS automatically provisions the servers, load balancers, and scaling groups for you.
• Best For: Developers who want to code without worrying about servers.

3. Software as a Service (SaaS)

• Definition: A completed product that is run and managed by the service provider. In most cases, people referring to SaaS are referring to end-user applications.
• Analogy: This is like riding a Bus. You have a specific destination, but you have zero control over the route, the vehicle, or the driver. You just pay a fare and use the service.
• Real World Example: Gmail, Dropbox, Zoom.
• AWS Example: Amazon Chime (communication service) or Amazon WorkMail.
• Best For: End-users who need a specific software solution instantly.

What is AWS? (The King of the Cloud)

AWS (Amazon Web Services) is the world’s most comprehensive and broadly adopted cloud platform. Born in 2006, it started as a side project to handle Amazon’s massive e-commerce scale and has evolved into a behemoth that powers the internet.

Who uses AWS?

• Netflix: Uses AWS for almost all its computing needs, including streaming content to you.
• NASA: Uses AWS to process images from Mars.
• McDonald’s: Uses AWS for its home delivery platform.
• Epic Games (Fortnite): Runs its massive multiplayer servers on AWS.

Why is AWS #1?

1. First Mover Advantage: They started years before Google or Microsoft.
2. Breadth of Services: AWS offers over 200 fully featured services from data centers globally.
3. Innovation: They release thousands of new features every year.

The AWS Global Infrastructure (The Map)

This is one of the most critical concepts for Day 1. You need to understand where your data lives. AWS is not just a “cloud” floating in the sky; it is physical hardware sitting in high-security bunkers across the planet.

1. Regions

A Region is a physical location in the world where AWS clusters data centers.

• Examples: us-east-1 (Northern Virginia), eu-west-1 (Ireland), ap-south-1 (Mumbai).
• Rule: Regions are completely isolated from each other. If the US region goes down due to a massive disaster, the Europe region is unaffected.
• How to choose a Region?
  1. Latency: Choose the region closest to your customers to speed up your website.
  2. Price: Some regions (like N. Virginia) are cheaper than others (like São Paulo) due to electricity/tax costs.
  3. Legal Compliance: If you are in Germany, GDPR might require your data to stay in the Frankfurt region.
  4. Service Availability: New services are often launched in N. Virginia first before rolling out globally.

2. Availability Zones (AZs)

Inside every Region, there are multiple Availability Zones.

• An AZ is one or more discrete data centers with redundant power, networking, and connectivity.
• Crucial Concept: AZs within a Region are connected with high-bandwidth, low-latency networking.
• Why does this matter? If you put your website on one server in one building, and that building catches fire, your site dies. In AWS, you put one copy of your site in AZ-A and another in AZ-B. If AZ-A burns down, AZ-B keeps running. This is called High Availability.

3. Edge Locations

There are many more Edge Locations than Regions.

• These are smaller sites used by Amazon CloudFront (Content Delivery Network).
• They cache content (images, videos) closer to the users.
• Example: If your server is in the USA but a user visits from Japan, the Edge Location in Tokyo will serve them a cached copy of the video, making it load instantly.

Core Cloud Concepts You MUST Know

To speak the language of AWS, you need to understand these four terms. Memorize them.

1. Scalability

The ability to accommodate a larger load by making resources bigger or adding more resources.

• Vertical Scaling (Scale Up): Adding more RAM or CPU to an existing server. (Like upgrading your laptop’s RAM). It has a limit—eventually, you max out the hardware.
• Horizontal Scaling (Scale Out): Adding more servers to the pool. (Instead of one super-computer, you use 10 small computers). This is the preferred “Cloud Way” because it’s limitless.

2. Elasticity

The ability to scale resources automatically based on demand.

• This is the “rubber band” effect.
• 8:00 AM: 2 servers running.
• 9:00 AM (Traffic spikes): System auto-expands to 10 servers.
• 10:00 PM (Traffic drops): System auto-shrinks back to 2 servers.
• Result: You don’t pay for idle servers.

3. Agility

The speed at which you can develop, deploy, and experiment.

• In the old days, trying a new idea took months of hardware procurement.
• In AWS, you can spin up 1,000 servers in minutes to test an idea. If it fails, shut them down 10 minutes later. The cost of failure becomes zero.

4. High Availability vs. Fault Tolerance

• High Availability: The system aims to remain accessible and operational at all times (usually measured in uptime, e.g., 99.99%). If a component fails, the system recovers quickly.
• Fault Tolerance: The system continues operating properly in the event of the failure of some of its components. It’s like a plane with 4 engines; if one breaks, the plane still flies perfectly.

The Shared Responsibility Model

Security is the #1 priority at AWS. But who is responsible for it? The answer is: Both of us.

AWS Responsibility: “Security OF the Cloud”

AWS protects the infrastructure that runs all the services.

• Physical Security: Guards, fences, biometric scanners at data centers.
• Hardware: Ensuring the servers and hard drives are not compromised.
• Network: Protecting the global fiber cables and power grids.
• Software: Patching the host operating system and virtualization layer.

Customer (Your) Responsibility: “Security IN the Cloud”

You are responsible for what you put inside the cloud.

• Guest OS: Patching the Windows/Linux OS you installed.
• Application: Ensuring your code doesn’t have bugs or vulnerabilities.
• Data: Encrypting your passwords and customer data.
• Access Management: Ensuring you don’t give your admin password to strangers.

AWS Pricing Fundamentals

How does Amazon charge you? It’s not a flat monthly fee like Netflix. It’s more complex, but generally follows three principles:

1. Pay-as-you-go: No long-term contracts. You pay by the hour or by the second.
2. Save when you reserve: If you commit to using AWS for 1 or 3 years (Reserved Instances), they give you a massive discount (up to 72%).
3. Pay less by using more: Volume discounts. The more storage space you use in S3, the cheaper the cost per Gigabyte becomes.

CAPEX vs. OPEX

• CAPEX (Capital Expenditure): Spending money upfront on physical assets (building a data center). This is the old way.
• OPEX (Operational Expenditure): Spending money on day-to-day operations. This is the AWS way. It is better for cash flow because you don’t need millions of dollars to start a business.

A Quick Tour of the Core Services (The “Big 5”)

AWS has 200+ services. You don’t need to know them all. On Day 1, you just need to know the acronyms for the “Big 5”.

1. EC2 (Elastic Compute Cloud): Virtual servers. The workhorse of AWS.
2. S3 (Simple Storage Service): Unlimited storage for files (images, videos, backups). It’s like a limitless Google Drive for your code.
3. RDS (Relational Database Service): SQL databases (MySQL, Postgres) managed by AWS.
4. VPC (Virtual Private Cloud): Your own private network inside AWS. You control the IP addresses and firewalls.
5. IAM (Identity and Access Management): The security guard. It controls who can access what in your AWS account.

Conclusion & Your Assignment

You have survived Day 1! We have covered the history of computing, the definition of cloud, global infrastructure, and the core concepts that make the cloud powerful.

Your Homework for Day 1:

1. Go to aws.amazon.com.
2. Create a Free Tier account. (You will need a credit card for identity verification, but you won’t be charged if you stay within free limits).
3. Log in to the AWS Management Console.
4. Just look around. Don’t touch anything yet. Just familiarize yourself with the search bar and the layout.

Tomorrow, on Day 2, we will dive deeper into those Core Services and explain exactly how EC2 and S3 work.

Stay tuned. The Cloud journey has just begun.