Module 4

Introduction to Going Global

The coffee shop is expanding globally, similar to how businesses expand applications using
AWS. While expanding, they must choose the best locations based on demand, cost, and
regulations—just like choosing AWS Regions.

The shop also creates smaller coffee carts that quickly serve popular items in different places.
This is similar to AWS edge locations, which deliver frequently used content faster to nearby
users.

To keep quality consistent everywhere, the shop standardizes recipes and automates processes.
Similarly, AWS uses tools like AWS CloudFormation to automate and maintain consistent
deployments across environments and regions.

How to Choose a Region or Set of Region

Just like a coffee shop considers demand and cost before opening new locations, businesses
must consider factors such as customer location, cost, and requirements when choosing AWS
Regions for their resources.

AWS edge Locations

Just like mobile coffee carts bring popular products closer to customers, AWS uses edge
locations to store cached content like images and videos closer to users, helping deliver content
faster with lower latency.

Infrastructure as Code and CloudFormation

As a coffee shop expands, it must keep the same quality and experience at every location.
Similarly, AWS services like AWS CloudFormation help automate cloud setup using
Infrastructure as Code (IaC), making deployments consistent, reliable, and easier to repeat as
the business grows.

Choosing AWS Regions

Key Considerations
1. Compliance
Compliance is important when choosing AWS Regions because different countries and areas
have different data protection laws. For example, companies operating in the European Union
must follow General Data Protection Regulation (GDPR) to protect customer data and privacy.
2. Proximity

When choosing an AWS Region, it’s important to select one close to your users. A nearby
Region reduces latency (delay), making applications faster and improving user experience and
system performance.

3. Feature Availability

When selecting an AWS Region, you should also check which AWS services and features are
available there because not all Regions offer the same services. For example, AWS GovCloud
Regions are specially designed for U.S. government security and compliance requirements.
4. Pricing

Pricing is an important factor when choosing an AWS Region because costs can vary between
Regions. Operational costs, taxes, and local data laws can affect the total cost of hosting
applications and storing data.

Diving Deeper into AWS Global Infrastructure

When choosing AWS infrastructure, businesses should plan for high availability and minimal
downtime. One way to do this is by using multiple Availability Zones (AZs). If one AZ fails,
the application automatically switches to another AZ, helping the service stay available without
users noticing problems.

Businesses can also use multiple AWS Regions for even better backup and disaster recovery. If
one entire Region has issues, traffic can fail over to another Region.

To make applications faster for users around the world, AWS provides Amazon CloudFront,
which delivers content like images, videos, APIs, and websites through nearby edge locations,
reducing loading time.

AWS edge services also include:

 Amazon Route 53 — routes users to applications using DNS

 AWS Global Accelerator — improves application performance

For extremely low-latency needs, AWS Outposts lets businesses run AWS services directly in
their own on-premises data centers.

Designing highly available Architectures

1. Deploying multi-Region and multi-AZ resources
Deploying resources across multiple AWS Regions and Availability Zones (AZs) improves
reliability and helps applications stay available even if failures occur. This creates a redundant
architecture for high availability.
Key Concepts

 High Availability
Keeps applications running with minimal downtime, even if some components fail.
 Agility
Helps businesses quickly adapt, deploy, and modify applications based on changing
needs.
 Elasticity
Automatically scales resources up or down depending on demand.

Edge Location

Besides AWS Regions and Availability Zones, AWS also has a global edge network with edge
locations placed around the world. These edge locations help deliver content and AWS services
faster with lower latency for users. Services like Amazon CloudFront use edge locations to
cache and deliver content quickly.
Key Elements of AWS Global Infrastructure

AWS Region

Regions are geographical areas around the world that are made up
of multiple data centers. These data centers provide scalable and
redundant infrastructure for hosting cloud services. Each Region
consists of multiple, isolated locations known as Availability Zones.
Each Region has three or more Availability Zones.

AWS AZ

Availability Zones are distinct locations within a Region, each

designed as an independent zone with its own power, networking,
and connectivity. Availability Zones maintain high availability and
fault tolerance for applications. Each Availability Zones consists of
one or more data centers.

Edge Location

Edge locations are strategically placed sites around the world that
cache content to deliver data, video, and applications with lower
latency and higher transfer speeds. Edge locations are considered a
vital part of the AWS content delivery network (CDN) and use
services like CloudFront to efficiently distribute data to end users.

Infrastructure and Automation

When managing many AWS resources across Regions or accounts, doing everything manually
can be slow and error-prone. Infrastructure as Code (IaC) solves this by defining infrastructure
in files, like a blueprint, so resources can be created automatically and consistently.

AWS CloudFormation is an IaC service that uses templates to define AWS resources in a
declarative way. CloudFormation automatically creates and configures the resources, helping
save time, reduce human errors, and deploy identical environments across multiple Regions or
accounts.

Additional Compute Services

AWS Elastic Beanstalk

 Simplifies deploying and managing applications on EC2

 Automatically handles:
o Infrastructure
o Networking
o Scaling
o Load balancing
  You provide application code and configuration
 Saves and reuses environment configurations

 Supports languages/frameworks like:

o Java, Python, .NET, [Link], Docker

Good For:

 Web applications
 REST APIs
 Mobile backends
 Microservices

AWS Batch

 Designed for:
o Large-scale data processing
o Simulations
o Complex calculations
 Automatically manages:
o Servers
o Scaling
o Infrastructure
 Distributes workloads across compute resources like EC2

Amazon Lightsail

 Simple and cost-effective hosting service

 Good for:
o Websites
o Small applications

Provides:

 VPS , Storage , Databases , Networking

AWS Outposts

 Extends AWS services to on-premises data centers

 Provides a hybrid-cloud environment
 Useful for:
o Low latency
o Data residency
o Hybrid deployments