AWS Cloud Fundamentals: What I Learned from Cloud Practitioner Essentials

AWS Cloud Fundamentals: What I Learned from Cloud Practitioner Essentials

Cloud computing was something I had heard about many times as a Computer Science student, but I wanted to understand what actually happens behind the applications and services we use every day.

I recently completed AWS Cloud Practitioner Essentials, and this article summarizes some of the concepts that helped me build a stronger foundation in AWS and cloud computing.

What is Cloud Computing?

In simple terms, cloud computing means using computing resources such as servers, storage, databases, networking, and other services over the internet instead of managing all the physical infrastructure ourselves.

AWS provides these resources as services that can be provisioned according to our requirements.

One of the biggest things I learned is that cloud computing is not simply about "using someone else's computer."

It is about being able to provision resources when needed, scale them according to demand, and pay based on usage, while AWS manages much of the underlying infrastructure.

---

1. Understanding Compute with Amazon EC2

One of the most important services I learned about was Amazon EC2 (Elastic Compute Cloud).

EC2 provides virtual servers in the AWS Cloud.

For example, suppose I want to deploy a Java Spring Boot application.

Instead of purchasing a physical server, I can launch an EC2 instance and run my application there.

The important concepts I learned include:

- EC2 instances
- Instance types
- AMIs
- Security groups
- Key pairs
- Elastic IP addresses
- Regions and Availability Zones

Different applications require different amounts of CPU, memory, storage, and networking capacity. EC2 provides different instance types so that we can choose resources according to our workload.

This helped me understand why cloud infrastructure is much more flexible than traditional physical servers.

---

2. Scaling Applications

An application may not receive the same amount of traffic all the time.

For example:

A college portal may receive normal traffic during most of the semester but experience a huge increase when examination results are released.

Keeping a large number of servers running all the time may waste resources.

This is where scalability becomes important.

AWS provides services such as:

- Elastic Load Balancing (ELB)
- EC2 Auto Scaling

A load balancer can distribute incoming requests across multiple servers.

Auto Scaling can automatically add or remove EC2 instances according to demand.

A simplified architecture looks like this:

Users
|
v
+-------------------+
| Load Balancer |
+-------------------+
/ \
/ \
v v
EC2 Instance EC2 Instance
| |
+------|------+
|
v
Application

The important idea for me was that scalability is not just about having more servers.

It is about automatically adjusting resources according to workload.

---

3. Understanding AWS Storage

Another major area I learned was AWS storage.

Different types of storage are designed for different requirements.

Amazon S3

Amazon S3 (Simple Storage Service) is object storage.

It can be used to store:

- Images
- Videos
- Documents
- Backups
- Logs
- Application files

For example, an application could store uploaded PDFs or images in S3 instead of storing them directly on an application server.

This is especially useful for applications that need to handle large amounts of files.

Amazon EBS

Amazon Elastic Block Store (EBS) provides block storage for EC2 instances.

I think of EBS as storage that can be attached to an EC2 instance and used like a disk.

It is useful when an application running on EC2 needs persistent block storage.

Amazon EFS

Amazon Elastic File System (EFS) provides a managed file system that can be accessed by multiple compute resources.

This makes it useful when multiple instances need access to the same files.

---

4. S3 vs EBS vs EFS

Understanding the difference between these services was one of the useful parts of learning AWS storage.

Service| Storage Type| Typical Use
S3| Object storage| Files, images, backups, data
EBS| Block storage| Storage attached to EC2
EFS| File storage| Shared files across instances

The key lesson is that there is no single "best" storage service.

The correct choice depends on how the application needs to access and use the data.

---

5. Regions and Availability Zones

Another important AWS concept is the difference between Regions and Availability Zones.

An AWS Region is a geographical area containing AWS infrastructure.

Within a Region, there are multiple Availability Zones.

This architecture helps applications achieve better availability and fault tolerance.

For example, instead of running an application in only one Availability Zone, an application can distribute its resources across multiple Availability Zones.

If one Availability Zone experiences a problem, the application can potentially continue operating using resources in another Availability Zone.

This introduced me to an important cloud principle:

«Design applications so that failure of a single component does not necessarily mean failure of the entire system.»

---

6. Scalability vs Elasticity

Before learning cloud computing, I often used the terms scalability and elasticity almost interchangeably.

AWS helped me understand the difference.

Scalability means increasing or decreasing resources to handle changing workloads.

Elasticity goes a step further by allowing resources to automatically adjust according to demand.

For example, if traffic suddenly increases, Auto Scaling can launch additional EC2 instances.

When traffic decreases, unnecessary instances can be removed.

This allows applications to respond dynamically to workload changes.

---

7. The Shared Responsibility Model

One of the most important concepts I learned is the AWS Shared Responsibility Model.

Security in the cloud is shared between AWS and the customer.

AWS is responsible for security of the cloud.

Customers are responsible for security in the cloud, depending on the services they use.

For example, AWS manages the physical infrastructure and data center security, while customers are responsible for things such as configuring access permissions and protecting their application data.

This changed the way I think about cloud security.

Using a managed cloud service does not mean that security becomes completely AWS's responsibility.

---

8. What I Took Away from the Course

The biggest takeaway from Cloud Practitioner Essentials was not memorizing individual AWS services.

It was learning how to think about cloud architecture.

When designing an application, I can now start asking questions such as:

- Where should my application run?
- Where should my files be stored?
- How will my application handle increased traffic?
- What happens if one server fails?
- How can I make the system highly available?
- Who is responsible for securing each part of the system?
- Which AWS service fits the actual requirement?

These questions are much more valuable than simply remembering service names.

---

My Next Step

As a Computer Science student interested in backend development, I want to go beyond cloud fundamentals and start applying these concepts to real applications.

My next focus is to explore AWS services more deeply and understand how cloud services can be integrated with backend applications built using technologies such as Java and Spring Boot.

Completing Cloud Practitioner Essentials gave me the foundation. Now the goal is to turn that knowledge into hands-on experience.

Final Thoughts

Cloud computing initially seemed like a huge collection of unfamiliar services.

After completing the course, I realized that the important part is understanding why a service exists and what problem it solves.

EC2 is not just a virtual server.

S3 is not just storage.

Auto Scaling is not just another AWS feature.

Each service solves a particular infrastructure problem, and together these services can be used to build applications that are scalable, available, and resilient.

This is just the beginning of my AWS learning journey, and I look forward to building more projects and gaining hands-on cloud experience.