Module 2: Introducing Cloud

Architecting
AWS Academy Cloud Architecting

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Module overview
Sections
1. What is cloud architecting?
2. The Amazon Web Services (AWS) Well-Architected
Framework
3. Best practices for building solutions on AWS
4. AWS global infrastructure

Knowledge check

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 2
Module objectives
At the end of this module, you should be able to:
• Define cloud architecture
• Describe how to design and evaluate architectures using the AWS Well-
Architected Framework
• Explain best practices for building solutions on AWS
• Describe how to make informed decisions on where to place AWS
resources

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 3
 A large architecture
Region VPC
Public Private subnet Private subnet
subnet

Availability
Zone 2
Amazon
CloudFron
t NAT EC2 ElastiCach Amazon Amazon
gateway instances e for RDS EFS
Interne Memcache standby mount
t d instance target
gatewa Application Amazon Amazon
y EC2 Auto EFS
Load
Amazon Scaling
Balancer
Public Private subnet Private subnet
Route subnet
Availability

53
Zone 1

NAT EC2 ElastiCach Amazon Amazon

Users Static gateway instances e for RDS EFS
website Memcache primary mount
d instance target
on S3
© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 4
Section 1: What is cloud
architecting?
Module 2: Introducing Cloud Architecting

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserve
Architectural need

Around 2000, Amazon was struggling to make its

new shopping website highly available and scalable.

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 6
Origins of AWS
• According to AWS CEO Andy Jassy, at the time, Amazon
ecommerce tools were “a jumbled mess”

• Applications and architectures were built without proper planning

• It was difficult to separate services from each other

• Solution: Amazon created a set of well-documented APIs,

which became the company’s standard for service
development

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 7
Problems persisted
• Amazon still struggled to build applications quickly.

• Database, compute, and storage components took 3 months to build.

• Each team built their own resources, with no planning for scalability or
re-usability.

• Solution: Amazon built internal services to create highly

available, scalable, and reliable architectures on top of its
infrastructure. In 2006, Amazon started selling these services
as AWS.
© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 8
Cloud architecture

These are my Structure design Completed structure

business goals
and
requirements…

Customer Building crew

(Decision maker) Archite (Delivery team)
ct
© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 9
Section 1 key • Cloud architecture is the practice of
applying cloud characteristics to a
takeaways solution that uses cloud services and
features to meet an organization’s
technical needs and business use
cases
• You can use AWS services to create
highly available, scalable, and reliable
architectures

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 10
Section 2: The AWS Well-
Architected Framework
Module 2: Introducing Cloud Architecture

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserve
Pillars of the AWS Well-Architected Framework

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 12
Security pillar

Identity Traceability Security at all Risk assessment

foundation layers and mitigation
strategies

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 13
Operational Excellence pillar

• The ability to run and monitor systems

• To continuously improve supporting process and procedures

Deployed Updated Operated

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 14
Reliability pillar
• Recover quickly from infrastructure or service disruptions

• Dynamically acquire computing resources to meet demand

• Mitigate disruptions such as:

• Misconfigurations

• Transient network issues

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 15
Performance Efficiency pillar
• Choose efficient resources and maintain their efficiency as
demand changes

• Democratize advanced technologies

• Employ mechanical sympathy

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 16
Cost Optimization pillar
• Measure efficiency

• Eliminate unneeded expense

• Consider using managed services

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 17
Sustainability pillar
• Understand your impact

• Establish sustainability goals

• Maximize utilization

• Anticipate and adopt new, more efficient hardware and

software offerings

• Reduce the downstream impact of your cloud workloads

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 18
The AWS Well-Architected Tool

• Helps you review the state of your workloads and

compares them to the latest AWS architectural
best practices
• Gives you access to knowledge and best
AWS
Well-Architected practices used by AWS architects, when you need
Tool it
• Delivers an action plan with step-by-step
guidance on how to build better workloads for the
cloud
• Provides a consistent process for you to review
and measure your cloud architectures

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 19
 • The AWS Well-Architected Framework
Section 2 key provides a consistent approach to evaluate
takeaways cloud architectures and guidance to help
implement designs
• The AWS Well-Architected Framework is
organized into six pillars
• Each pillar documents a set of foundational
questions that enable you to understand if a
specific architecture aligns well with cloud
best practices
• The AWS Well-Architected Tool helps you
review the state of your workloads and
compares them to the latest AWS
architectural best practices

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 20
Section 3: Best practices for
building solutions on AWS
Module 2: Introducing Cloud Architecting

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserve
Design tradeoffs
• Evaluate tradeoffs so you can select an optimal approach
• Examples of tradeoffs include:
• Trade consistency, durability, and space for time and latency to deliver
higher performance
• Prioritize speed to market of new features over cost
• Base design decisions on empirical data

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 22
 1. Enable scalability (1 of 2)

Ensure that your architecture can

handle changes in demand.
Application
servers at Anti-pattern
full
capacity
Users Administrat
cannot or manually
access launches
application New server new server
takes time
to launch

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 23
 1. Enable scalability (2 of 2)

Ensure that your architecture can

handle changes in demand.

Application
servers at
alarm threshold Best practice
Users never
experience a Amazon EC2
service Auto Scaling
interruption is alerted
New server is and scales
ready before out
capacity is
reached

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 24
2. Automate your environment

Where possible, automate the provisioning,

termination, and configuration of resources.
Automatically
logs action to
Anti-pattern Best practice a change
management
Amazon EC2 Auto solution
Application Scaling
server automatically
crashes launches and
Administrator Application configures
manually launches server identical server
and configures new crashes
server Amazon
CloudWatch Automatically
Users manually
automatically notifies
notify
detects unhealthy administrator
administrator
instance
© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 25
3. Treat resources as disposable

Take advantage of the dynamically

provisioned nature of cloud computing.

Anti-pattern Best practice

• Over time, different servers end up • Automate deployment of new resources
with different configurations with identical configurations
• Resources run when they’re not • Terminate resources that are not in use
needed • Switch to new IP addresses automatically
• Hardcoded IP addresses prevent • Test updates on new resources, and then
flexibility replace old resources with updated ones
• It can be difficult or inconvenient to
test new updates on hardware that's in
use © 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 26
4. Use loosely coupled components

Design architectures with

independent components.

Anti-pattern Best
Web practice Web
servers servers

Elastic Load
Balancing
Applicatio Applicatio
n servers n servers
Web servers tightly
coupled to application Decoupled with a load
servers balancer

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 27
5. Design services, not servers

Use the breadth of AWS services.

Don't limit your infrastructure to
servers.

Anti-pattern Best
• Simple applications run on persistent
practice
• When appropriate, consider using containers
servers or a serverless solution
• Message queues handle communication
• Applications communicate directly with
between applications
one another
• Static web assets are stored externally, such
• Static web assets are stored locally on as on Amazon Simple Storage Service
instances (Amazon S3)
• Backend servers handle user • User authentication and user state storage
authentication and user state storage are handled by managed AWS services

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 28
6. Choose the right database solution

Match technology to the workload,

not the other way around.

Things to consider:

• Read and write needs • Latency requirements

• Total storage requirements • Maximum concurrent users to
support
• Typical object size and nature of
• Nature of queries
access to these objects
• Required strength of integrity
• Durability requirements controls

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 29
7. Avoid single points of failure (1 of 2)

Assume everything
fails. Then, design Where possible, use
backward. redundancy to prevent single
points from bringing down an
entire system.

Anti-pattern

Application servers Database

server
© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 30
7. Avoid single points of failure (2 of 2)

Best practice
Create a secondary
(standby) database
Replication server and replicate the
Database Database data.
server server
Applicatio (primary) (secondary
n servers )

Secondary server picks

up the load.
Replication
Database
Main database server
Applicatio server goes offline. (secondary
n servers )
© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 31
8. Optimize for cost

Take advantage of the flexibility of

AWS to increase your cost efficiency.

Things to consider:

• Are my resources the right • How often will I need to use

size and type for the job? this resource?
• What metrics should I • Can I replace any of my
monitor? servers with managed
• How do I make sure to turn services?
off resources that are not in
use? © 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 32
9. Use caching

Caching minimizes redundant data retrieval

operations, improving performance and cost.

Anti-pattern Best practice

Caching
S3 bucket with S3 bucket
with data Amazon with data
CloudFront

Three requests of The second, third, and

equal latency and nth
cost. requests are at a lower
latency and cost.
© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 33
10. Secure your entire infrastructure

Build security into every layer

of your infrastructure.

Things to consider:

• Isolate parts of your infrastructure • Use managed services

• Encrypt data in transit and at rest • Log access of resources
• Enforce access control granularly,
• Automate your deployments to
using the principle of least privilege
keep security consistent
• Use multi-factor authentication (MFA)

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 34
 • As you design solutions, evaluate tradeoffs
Section 3 key and base your decisions on empirical data
takeaways • Follow these best practices when building
solutions on AWS –
• Enable scalability
• Automate your environment
• Treat resources as disposable
• Use loosely-coupled components
• Design services, not servers
• Choose the right database solution
• Avoid single points of failure
• Optimize for cost
• Use caching
• Secure your entire infrastructure
© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 35
Section 4: AWS global
infrastructure
Module 2: Introducing Cloud Architecting

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserve
AWS Regions
• An AWS Region is a geographical
area
• Each AWS Region consists of two or
more Availability Zones
• Communication between Regions
uses AWS backbone network
infrastructure
• You enable and control data
replication across Regions
Example: London Region

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 37
AWS Availability Zones
• Each Availability Zone is –
AWS Cloud
• Made up of one or more data centers
Region eu-west-1
• Designed for fault isolation Availability Zone eu-west-1a
• Interconnected with other Availability Data center

Zones in a Region using high-speed private Data center

links
Data center
• For certain services, you can choose
Availability Zone eu-west-1b
your Availability Zones
• AWS recommends replicating across Availability Zone eu-west-1c

Availability Zones for resiliency

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 38
AWS Local Zones
• Enable you to run latency-sensitive portions of applications
closer to end users and resources in a specific geography
• Are an extension of an AWS Region where you can use AWS
services in geographic proximity to end users
• Let you place AWS compute, storage, database, and other
select services closer to large population, industry, and IT
centers where no Region exists today
• Are managed and supported by AWS
• Los Angeles (LA) AWS Local Zone is available by invitation

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 39
AWS data centers
• Data centers are where the data
resides and data processing occurs
• A data center typically has tens of
thousands of servers
• All data centers are online and
serving customers
• AWS custom network equipment –
• Is sourced from multiple ODMs
• Has a customized network protocol stack

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 40
AWS Points of Presence

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 41
Section 4 key • The AWS global infrastructure consists of
Regions, Availability Zones, and edge
takeaways locations
• Your choice of a Region is typically based
on compliance requirements or to reduce
latency
• Each Availability Zone is physically
separate from other Availability Zones
and has redundant power, networking,
and connectivity
• Edge locations and Regional edge caches
improve performance by caching content
closer to users

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 42
Module wrap-up
Module 2: Introducing Cloud Architecting

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserve
Module summary
In summary, in this module, you learned how to:
• Define cloud architecture
• Describe how to design and evaluate architectures using the AWS Well-
Architected Framework
• Explain best practices for building solutions on AWS
• Describe how to make informed decisions on where to place AWS
resources

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 45
Complete the knowledge check

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 46
Additional resources
• AWS Global Infrastructure page
• Interactive AWS Global Infrastructure map
• AWS Well-Architected Framework whitepaper
• Security Pillar whitepaper
• Operational Excellence Pillar whitepaper
• Reliability Pillar whitepaper
• Performance Efficiency Pillar whitepaper
• Cost Optimization Pillar whitepaper
• Sustainability Pillar whitepaper
© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 47
Thank you

Corrections, feedback, or other questions?

Contact us at https://support.aws.amazon.com/#/contacts/aws-training.
All trademarks are the property of their owners.

© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved.