• Where data is stored (EBS, EFS, S3)

• How users reach applications (Route 53)

Now let's understand how AWS makes applications faster for users accross the world.

This is where CloudFront comes in.

What is CDN (Content Delivery Network)?

• A CDN is a network of servers located in different geographical locations.

• Instead of serving content from one central server, CDN delivers content from the nearest server to the user.

Why CDN is needed?

Without CDN:

• Requests travel long distances.

• High latency

• Slow loading

With CDN:

• Faster response

• Reduces latency

• Better user experience

What is Amazon CloudFront?

Amazon CloudFront is AWS's Content Delivery Network (CDN) service.

It delivers content such as:

• Images

• Videos

• APIs

• Static websites

What are Edge Locatios?

• Edge locations are AWS data centers located closer to users.

• CloudFront caches content in these locations so that users get data from the nearest point.

Example:

• User in India ---> gets content from nearby edge location

• User in US ---> gets content from US edge location

This reduces latency significantly.

How CloudFront Works?

1. User requests a file (Image/Video/API)

2. Request goes to nearest edge location

3. If content is available -> returned immediately (cache hit)

4. If not -> fetched from origin (cache miss)

5. Content is stored in edge location for future requests

Cache Hit vs Cache Miss

Cache Hit

• Content already available in edge location

• Fast response

Cache Miss

• Content not available

• Fetched from origin

• Stored for next request

CloudFront Integration with AWS Services

CloudFront works with multiple AWS services to improve performance.

1. CloudFront + S3

Used for:

• Static website hosting

• Images, CSS, JS files

Flow:

User --> CloudFront --> S3

2. CloudFront + Load Balancer (ALB)

Used for:

• Dynamic applications

• APIs

Flow:

User --> CloudFront --> Load Balancer --> EC2

Benefits of CloudFront

• Low latency (faster content delivery)

• Global edge locations

• Reduced load on origin servers

• High scalability

• Improved user experience

• Secure content delivery

• Cost optimization (less origin traffic)

Real-Time Use Cases

CloudFront is widely used in real-world applications:

1. Video Streaming Platforms

Deliver videos smoothly without buffering

2. E-commerce Websites

Fast loading of product images

3. News Websites

Quick delivery of articles worldwide

4. Static Website Hosting

S3 + CloudFront for fast performance

5. API Acceleration

Faster API responses for global users

6. Gaming Applications

Deliver game assets globally

7. Media & Entertainment

Content distribution across regions

8. Software Downloads

Fast delivery of large files

Real-Time Architecture Example

Let's combine everything

1. User accesses website

2. Route 53 resolves domain

3. Request goes to CloudFront

4. CloudFront serves from edge location

5. If needed, fetches from S3 or EC2

This improves performance and reduces server load

When to use CloudFront

Use CloudFront when:

• You want faster content delivery

• Your users are globally distributed

• You want to reduce latency

• You are serving static or dynamic contrnt

• You need CDN for your application

• You want to reduce load on servers

Conclusion

--> Amazon CloudFront plays a key role in improving application performance.

--> It helps deliver content faster by caching data at edge locations close to users.

--> When combined with services like S3, EC2 and Load balancer, CloudFront helps build high-performance, scalable and globally available applications.

--> Understanding CloudFront is important for anyone working with AWS and DevOps.

=> But how does the browser know where the website is hosted?

=> This is where DNS (Domain Name System) works behind the scenes.

=> In AWS, DNS is managed using Amazon Route 53, a highly available and scalable domain in name system service.

What is DNS (Domain Name System)?

=> DNS works like a phonebook of the internet.

=> Instead of remembering IP addresses such as:

=> We use domain names such as: example.com

=> DNS translate domain names into IP addresses so browsers can locate the correct server.

Eg: 142.250.x.x

=> Without DNS, we would need to remember numerical IP addresses for every website.

What is Amazon Route 53?

Amazon Route 53 in AWS's DNS service that helps route internet traffic to the correct resources.

It connects domain names to:

• EC2 instances

• Load Balancers

• S3 buckets

• CloudFront distributions

• Other web servers

Route 53 is designed to provide:

• High availability

• Low latency

• Scalability

• Reliable domain routing

Why it is called Route 53?

The name comes from port 53, which is the standard port used for DNS services.

How Route 53 Works?

When a user enters a domain name in a browser:

1. The request goes to DNS.

2. Route 53 checks the hosted zone records.

3. Route 53 returns the IP address.

4. Browser connects to the server.

5. Website loads.

This process happens in milliseconds.

Hosted Zones in Route 53:

=> A hosted zone is a container for DNS records.

=> It stores information about how traffic should be routed for a domain.

=> Example hosted zone: example.com

=> Inside the hosted zone, we define records such as:

• example.com -> Load Balancer IP

• www.example.com -> EC2 IP

Types of Hosted zones:

1. Public Hosted Zone:

Used for websites accessible from the internet.

Example: Company website

2. Private Hosted Zone:

Used for internal applications inside VPC.

Example: Internal company tools

DNS Record types in Route 53

DNS records tell Route 53 where to send traffic.

Some common record types:

A Record (Address Record)

Maps domain name to IPv4 address.

Example:

example.com -> 192.168.1.1

AAAA Record

Maps domain name to IPv6 address.

CNAME Record

Maps one domain name to another domain name.

Example:

www.example.com -> example.com

Alias Record:

Used to map domain to AWS resources such as:

• Load Balancer

• CloudFront

• S3 website

Alias records are commonly used in AWS architectures.

Routing Policies in Route 53

=> Routing policies define how ROute 53 responds to DNS queries.

=> Different routing strategies can be used depending on application needs.

1. Simple Routing

Routes traffic to a single resource.

Example:

All users go to one server.

2. Weighted Routing

Traffic is split based on percentages.

Example:

70% -> Server A

30% -> Server B

Useful for testing new versions.

3. Latency-based Routing

-> Routes traffic to the server with lowest latency.

-> Improves performance for global users.

4. Failover Routing

-> Routes traffic to backup server if primary fails.

-> Supports high availability.

5. Geolocation Routing

Routes users based on geographic location.

Example:

• Users from India -> Asia server

• Users from US -> US server

Health Checks in Route 53

-> Health checks monitor application endpoints.

-> If a server becomes unhealthy, Route 53 can redirect traffic to another healthy resource.

Example:

-> Primary server fails -> traffic moves to backup server.

-> This helps maintain availability.

Health checks can monitor:

• Website endpoints

• Ip addresses

• Load Balancers

Real-Time Architecture Example

In real-world AWS architecture:

1. User enters domain name

2. Route 53 resolves domain

3. Traffic goes to Load Balancer

4. Load Balancer distributes traffic to EC2 instances

5. Application loads

Route 53 acts as the entry point to the application.

Common Use Cases of Route 53

• Hosting websites

• Connecting domain to AWS resources

• Load balancing traffic globally

• Improving application availability

• Disaster recovery routing

• Blue-green deployments

• Canary deployments

• Multi-region applications

• Routing traffic to closest server

• Domain management

Benefits of using Route 53

• Highly reliable DNS service

• Scalable infrastructure

• Low latency routing

• Supports multiple routing policies

• Integration with AWS services

• Improves application availability

• Supports failover routing

• Global service

When to use Route 53

Use Route 53 when:

• You want to connect domain name to AWS resources

• You need highly available DNS

• You want traffic routing control

• You need health monitoring

• You want multi-region routing

• You need reliable domain resolution

Conclusion

• Amazon Route 53 plays an important role in connecting users to applications.

• It works as a bridge between domain names and cloud resources.

• Understanding DNS and Route 53 helps in designing scalable and highly available architectures in AWS.

• It is an essential service for cloud engineers and DevOps professionals.

In this blog, we will understand the differences between Amazon EBS, Amazon EFS and Amazon S3 along with real-time examples and when to use each service.

Types of Storage in AWS

There are three main types of storage used in cloud environments:

1. Block Storage:

Block storage divides data into blocks and stores them separately. Each block works like an independent disk. It is mainly used with virtual machines such as EC2.

Example:

• Operating System

• Databases

• Application files

AWS service: Amazon EBS

2. File Storage:

-> File storage stores data in a hierarchical structure (folders and files).

-> Multiple systems can access the same files at the same time.

Example:

• Shared folders

• Content management system

• Development environments

AWS service: Amazon EFS

3. Object Storage:

-> Object storage stores data as objects inside buckets. Each object contains data, metadata and a unique ID.

-> It is highly scalable and commonly used for storing large amounts of unstructured data.

Example:

• Images

• Videos

• Backup files

• Logs

AWS Service: Amazon S3

Amazon EBS (Elastic Block Storage)

-> Amazon EBS provides block-level storage that can be attached to EC2 instances.

-> It works like a hard disk for virtual servers. EBS volumes are highly reliable and designed for applications that require consistent performance.

Features:

• Attached to one EC2 instance at a time.

• High performance storage.

• Data persists even after instance stops.

• Suitable for databases and OS storage.

Common Use Cases:

• Hosting operating system files.

• Running databases like MySQL or PostgreSQL.

• Transaction based applications.

• Applications requiring low latency.

• Boot volumes of EC2.

• ERP or financial systems.

Real-time example:

If you launch an EC2 instance to host a web application, the application files and operating system can be stored in EBS.

Amazon EFS (Elastic File System)

-> Amazon EFS provides file storage that can be accessed by multiple EC2 instances at the same time.

-> It is useful when multiple servers need shared access to the same files.

Features:

• Shared file system

• Automatically scales storage

• Supports multiple EC2 connections

• Highly available

Common Use Cases:

• Shared application files

• Website content shared across servers

• Container storage

• Machine learning workloads

• Bog data analytics

• Media processing workflows

• Home directories for multiple users

• CI/CD pipelines storing shared build files

Real-time example:

If multiple EC2 instances are running a website, EFS allows all servers to access the same files.

Amazon S3 (Simple Storage Service)

-> Amazon S3 provides object storage that allows storing unlimited data.

-> Data is stored in buckets and accessed using URLs.

Features:

• Highly scalable

• Very durable

• Cost effective

• Accessible from anywhere

• Suitable for storing large files

Common Use Cases:

• Image storage for websites

• Video storage

• Backup and restore

• Log storage

• Static website hosting

• Data lakes

• Archival storage

• Storing documents

• Application assets (CSS, JS files)

Real-time example:

A company can store product images or user uploads in S3 and access them whenever needed.

Difference between EBS vs EFS vs S3

When to use which storage?

Use EBS when:

• You need storage for one EC2 instance

• You need high performance disk

• You are running databases

• You need persistent storage

Use EFS when:

• Multiple EC2 instances need shared access

• You need scalable file storage

• Applications require shared folders

• You need centralized storage

Use SS when:

• You want to store large files

• You need backup storage

• You want highly durable storage

• You need static website hosting

• You want low-cost storage

• You need long-term archive

Real-Time Architecture Example

In real applications, these storage services are often used together.

Example:

• EC2 instances run application code

• EBS stores operating system and database files

• EFS shares files between multiple servers

• S3 stores images, backups and logs

This combination helps build scalable and reliable cloud applications.

Conclusion

-> AWS provides different storage services to meet different requirements.

-> Amazon EBS is useful for block-level storage attached to EC2 instances.

-> Amazon EFS is useful when multiple EC2 instances need shared file access.

-> Amazon S3 is ideal for storing large amounts of unstructured data.

Understanding these storage services helps in designing efficient, scalable and cost-effective cloud architectures and choosing the right storage option is an important step in building strong DevOps and cloud solutions.

Now let’s move one step further and understand how AWS helps us build highly available, scalable and production-ready architectures.

In this blog, we’ll cover:

• Elastic Load Balancer (ELB)

• Auto Scaling

• RDS (Relational Database Service)

• CloudWatch

These services are essential when moving from a basic setup to a real-world deployment.

1. Elastic Load Balancing (ELB):

When you deploy an application on a single EC2 instance, all traffic goes tp that one server.

But what happens if:

• Traffic suddenly increases?

• The instance crashes?

• You want high availability?

This is where Elastic Load Balancing comes in.

What is ELB?

• Elastic Load Balancing automatically distributes incoming application traffic across multiple EC2 instances.

• Instead of users connecting directly to EC2, they connect to the Load Balancer, which forwards traffic to healthy instances.

Types of Load Balancers:

• Application Load Balancer (ALB) - Layer 7 (HTTP / HTTPS)

• Network Load Balancer (NLB) - Layer 4 (TCP / UDP)

• Gateway Load Balancer - For advanced network appliances

1. Auto Scaling:

   Handling traffic manually is not practical in production .

Imagine:

• Traffic spikes during scales.

• Traffic drops at night.

You don’t want to pay for unused servers.

What is Auto Scaling?

Amazon EC2 Auto scaling automatically adjusts the number of EC2 instances based on demand.

How it Works?

• Minimum instances (always running)

• Desired capacity

• Maximum instances

• Scaling policies (based on CPU, traffic etc.,)

Auto scaling works perfectly with:

• EC2

• Load Balancer

Together they provide:

→ High availability

→ Cost optimization

→ Automatic scaling

1. Amazon RDS (Relational Database Service)

• Applications usually need a database.

• Instead of manaually installing and managing a database on EC2, AWS provides a managed solution.

What is RDS?

Amazon RDS is a managed relational database service.

It supports:

• MySql

• PostgreSQL

• MariaDB

• SQL Server

• Oracle

Key Features:

• Automated backups

• Multi-AZ deployment

• Automatic patching

• Read replicas

• High availability

With Multi-AZ, AWS automatically creates a standby database in another Availability Zone.

If the primary fails, traffic switches automatically.

1. Amazon CloudWatch

Once your application is running, you must monitor it.

Without monitoring:

• You won't know when CPU is high.

• You won't know when instances fail.

• You won't know detect unusual behaviour.

What is CloudWatch?

Amazon CloudWatch is AWS's monitoring and observability service.

What it provides?

• Metrics (CPU, memory, disk usage)

• Logs

• Alarms

• Dashboards

• Event triggers

Example:

If CPU usage exceeds 80%, CloudWatch can trigger Auto Scalling to launch new instances.

That's automation in action.

How These Services Work Together?

Let's connect everything:

1. Users access the application.

2. Load Balancer distributes traffic.

3. Auto Scaling adjusts the number of EC2 instances.

4. EC2 instances connect to RDS.

5. CloudWatch monitors the entire system.

This creates:

• Scalable

• Highly available

• Fault-tolerant

• Production-ready architecture

Conclusion

Building applications on AWS is not just about launching EC2 instances.

To design real-world systems, you must use:

• Load balancing for traffic distribution.

• Auto scaling for elasticity

• RDS for managed databases

• CloudWatch for monitoring and automation

These services work otgether to create reliable, scalable cloud solutions.