AWS Introduction
What Is AWS?
AWS (Amazon Web Services) is a cloud computing platform. It rents compute, storage, networking, and managed services over the internet—billed by usage instead of a flat hardware purchase.
Hierarchy:
Account → Region → Availability Zone → resources
Core pieces beginners meet first:
IAM identity & permissions
EC2 virtual servers
S3 object storage
ALB / Route 53 / CloudFront traffic & DNS / CDNAWS launched in 2006 and remains one of the most widely used clouds. This page is the gateway to CodeToFun’s AWS guides—EC2, load balancing, S3, and more have their own pages.
Why Use AWS?
Cloud lets a side project and a growing product share the same building blocks: provision in minutes, scale for a traffic spike, then scale back down.
| Need | How AWS helps |
|---|---|
| No hardware rack | Launch an EC2 instance or S3 bucket in minutes |
| Pay for use | Billed by the second or hour for many services |
| Global reach | Regions worldwide; place resources near users |
| Managed pieces | Load balancers, DNS, CDN, and certificates as services |
Key ideas early
| Idea | Why it matters |
|---|---|
| Region | Geographic area (e.g. ap-south-1) |
| Availability Zone | Isolated data center inside a Region |
| IAM | Who can do what in your account |
| Free Tier | Limited learning credits—always set a billing alarm |
How AWS Fits Together
Think in layers. You pick a Region, create resources, then route users to them.
| Layer | What it does | Example |
|---|---|---|
| Identity | Controls access | IAM users, roles, policies |
| Compute | Runs your code | EC2 instances |
| Storage | Keeps files and backups | S3 buckets |
| Networking | Routes and names traffic | ALB, Route 53, CloudFront |
| Security (TLS) | HTTPS certificates | ACM |
Cheat sheet — common services
| Service | Role | Guide |
|---|---|---|
| EC2 | Virtual servers | Launch an EC2 instance |
| Security groups | Instance firewall rules | Security groups |
| ENI | Virtual network cards | Network interfaces |
| Lambda | Serverless functions | AWS Lambda |
| S3 | Object storage | Amazon S3 |
| ALB | HTTP(S) load balancing | Application Load Balancer |
| NLB | TCP/UDP/TLS load balancing | Network Load Balancer |
| Route 53 | DNS | Route 53 |
| CloudFront | CDN / edge cache | CloudFront |
| WAF | Web application firewall | AWS WAF |
| API Gateway | Managed APIs | Amazon API Gateway |
| ACM | TLS certificates | Certificate Manager |
What Should Beginners Learn First?
A simple mental map of the first concepts you will see in the console:
| Concept | Meaning |
|---|---|
| Account | Your AWS billing and resource boundary |
| Region | Where resources live geographically |
| Availability Zone | Isolated data center inside a Region |
| IAM user / role | Identity used by people or services |
| EC2 instance | A virtual machine that runs your app |
| S3 bucket | A container for files (objects) |
| Security group | Virtual firewall for EC2 traffic |
aws configure
aws sts get-caller-identity
aws s3 ls
aws ec2 describe-instances --region ap-south-1AWS vs Traditional Hosting
If you know shared hosting or a single VPS, map the ideas like this:
| Traditional hosting / VPS | AWS |
|---|---|
| One server plan | Separate services you combine |
| Flat monthly fee | Pay for what you use |
| Scale by upgrading the box | Scale instances, storage, and CDN independently |
| Host panel for files and DNS | Console / CLI / APIs for each service |
| Simple to start | More powerful—and more to learn (IAM, Regions) |
When to choose which
| Prefer AWS when… | Prefer simple hosting when… |
|---|---|
| You need scale, redundancy, or many services | You want the fastest path for a small site |
| You want fine-grained control (EC2, ALB, S3) | A fixed VPS or WordPress host is enough |
| You are learning cloud / DevOps skills | You prefer not to manage IAM and networking yet |
Your First AWS CLI Check
Install the AWS CLI, run aws configure with an IAM user’s access key, then confirm who you are before creating resources.
aws sts get-caller-identityHow It Works
1. Authenticate. The CLI uses credentials from aws configure (stored under ~/.aws/).
2. Call STS. get-caller-identity asks AWS who the current credentials belong to.
3. Read the ARN. The response shows your account ID and the IAM user or role ARN—proof the CLI works.
Never commit access keys to Git. Create an IAM user for daily work and avoid using the root account. Next, follow Launch an EC2 instance.
Where Is AWS Used?
Common workloads that map well to AWS building blocks:
| Use case | Why AWS fits |
|---|---|
| Web apps & APIs | EC2 (or containers) behind an ALB |
| Static assets & backups | S3 for files, logs, and snapshots |
| Global content delivery | CloudFront caches near users |
| Custom domains | Route 53 for DNS records |
| HTTPS at scale | ACM certificates on ALB or CloudFront |
| Learning cloud skills | Same services used in real production stacks |
Key Takeaways
- AWS rents cloud building blocks—compute, storage, and networking—by usage.
- Hierarchy: account → Region → Availability Zone → resources.
- Start with: IAM safety, then EC2 and S3.
- CLI check:
aws sts get-caller-identitybefore creating resources.
One line: AWS is on-demand cloud infrastructure—next, launch an EC2 instance.
Frequently Asked Questions
Did you know?
AWS runs in Regions made of multiple Availability Zones. Prefer a Region close to your users, keep backups across AZs, and use IAM least privilege—never put long-lived access keys in client-side code.
Next: Launch an EC2 Instance
Create a virtual server and take your first hands-on step in AWS.
About the author
11 people found this page helpful