Cloud computing is no longer optional for developers. Whether you build frontend applications, APIs, or full-stack systems, understanding how cloud infrastructure works is becoming a core skill.
As a developer transitioning into cloud fundamentals, I recently started learning Amazon Web Services (AWS). In this article, I’ll break down what I learned in Part 1 — from setting up a free AWS account to understanding IAM, EC2, and storage services like EBS and EFS.
If you’re just getting started with AWS, this guide will help you build a strong foundation.
1. Setting Up an AWS Free Tier Account
The AWS Free Tier allows beginners to practice without immediate costs. It includes:
- 750 hours per month of t2.micro or t3.micro EC2 instances (for 12 months)
- 5GB of Amazon S3 storage
- Limited usage of other core services
Important tip: Always enable billing alerts in the AWS Billing Dashboard. Even small configuration mistakes can lead to unexpected charges if limits are exceeded.
Learning cloud safely starts with understanding cost control.
2. What Is Cloud Computing?
Cloud computing means delivering computing services — servers, storage, databases, networking, and more — over the internet on a pay-as-you-go basis.
Instead of buying physical servers, you rent resources when needed.
Types of Cloud Service Models
IaaS (Infrastructure as a Service)
Example: Amazon EC2
You manage operating systems and applications, AWS manages hardware.
PaaS (Platform as a Service)
Example: AWS Elastic Beanstalk
You deploy applications without managing infrastructure.
SaaS (Software as a Service)
Example: Gmail or Google Docs
You simply use the software; infrastructure is fully managed.
Understanding these models is essential before diving into AWS services.
3. AWS Console and the Shared Responsibility Model
The AWS Management Console is the web-based interface where you configure services.
One of the most important concepts in AWS is the Shared Responsibility Model.
AWS is responsible for:
- Physical hardware
- Data centers
- Networking infrastructure
- Host operating systems
You are responsible for:
- Your data
- IAM users and permissions
- Application configuration
- Security group rules
Many beginners misunderstand this. AWS secures the cloud, but you must secure what you build inside it.
4. IAM (Identity and Access Management)
IAM controls who can access AWS resources and what actions they can perform.
Key components:
Users — Individual identities (e.g., developer accounts)
Groups — Collections of users with shared permissions
Policies — JSON documents defining permissions
Roles — Temporary credentials assigned to services
MFA (Multi-Factor Authentication) — Extra security layer for login
Best practice: Never use the root account for daily work. Create IAM users with limited permissions instead.
IAM is one of the most critical topics for AWS interviews and real-world security.
5. AWS CLI Setup
The AWS Command Line Interface (CLI) allows you to interact with AWS services directly from your terminal.
Steps:
- Install AWS CLI
- Run
aws configure - Enter Access Key
- Enter Secret Key
- Choose region
- Choose output format (JSON is common)
Example command:
aws s3 lsThe CLI is powerful for automation and scripting, especially when working with CI/CD pipelines.
6. IAM Roles and Security Tools
IAM Roles allow AWS services (like EC2) to securely access other services without storing credentials inside the instance.
Example:
Instead of saving S3 access keys inside an EC2 server, attach an IAM Role to the EC2 instance.
AWS also provides security tools such as:
- AWS CloudTrail (API activity tracking)
- AWS CloudWatch (monitoring)
- AWS Config (resource compliance)
Security is not optional in cloud environments. It must be designed from the beginning.
7. Amazon EC2 Basics
Amazon EC2 (Elastic Compute Cloud) provides virtual servers in the cloud.
Important concepts:
Instance Types
Different configurations based on CPU, memory, and workload type.
Example: t2.micro for lightweight applications.
Security Groups
Act as virtual firewalls controlling inbound and outbound traffic.
SSH Access
Used to connect to Linux instances securely via key pairs.
IAM Roles for EC2
Allow secure communication between EC2 and other AWS services.
Understanding EC2 is essential because most backend systems run on compute instances.
8. AWS Storage Services Overview
AWS provides multiple storage options depending on use case.
Amazon EBS (Elastic Block Store)
- Block storage attached to EC2
- Persistent storage
- Used for databases and OS volumes
AMI (Amazon Machine Image)
- Pre-configured template for launching EC2 instances
- Includes OS and installed software
EC2 Instance Store
- Temporary storage
- Data lost when instance stops
Amazon EFS (Elastic File System)
- Shared file storage
- Multiple EC2 instances can access simultaneously
Amazon FSx
- High-performance file systems
- Used for enterprise workloads
Choosing the right storage solution depends on durability, performance, and scalability requirements.
Key Takeaways from Part 1
- Cloud computing fundamentals are crucial before using services.
- IAM and security should be prioritized from day one.
- EC2 is the backbone of many cloud architectures.
- Storage services vary significantly based on use case.
- Understanding the Shared Responsibility Model prevents security mistakes.
Comments
Post a Comment