WKS402A Well-Architected Workshop

1© 2017 Amazon Web Services, Inc. and its affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Jeff Levine, Enterprise Solutions Architect
Chris Colthurst, Solutions Architect
April 19th, 2017
Well-Architected Workshop

2© 2017 Amazon Web Services, Inc. and its affiliates. All rights reserved.
What to Expect from the Session
Learn about
 The AWS Well-Architected Framework (5 pillars)
 Value proposition
 General design principles
 Best practices
Learn how to improve your cloud architectures and better
understand the business impact of your design decisions

Agenda
Introduction to Well-Architected
Walk through the example
Learn about each pillar,
then teams review and present back

“Are you Well-Architected?”
Strategies & best practices for architecting in the cloud
Questions that allow you to measure your architecture against
best practices
 How to address any shortcomings

“Are you Well-
Architected?”
Werner Vogels

Purpose of Well-Architected
Making informed decisions about architecture in the cloud,
understanding the potential impact of decisions
Questions are the starting point, you should think actively about
“what if” and failure scenarios
Not a binary “yes” or “no”, depends on business context

Value Proposition
Help Customers:
Consistent approach to reviewing architectures
Understand and reduce risk in your architecture
Learn best practices
Influence future architectures

AWS Well-Architected
Framework

The AWS Well-Architected Framework
Increases awareness of architectural best practices
Addresses foundational areas that are often neglected
Consistent approach to evaluating architectures
Composed of:
 Pillars
 Design principles
 Questions

Pillars of Well-Architected Framework
Security Reliability Performance
Efficiency
Cost
Optimization
Operational
Excellence

Design Principles
The Well-Architected Framework has identified a set of
design principles to facilitate good design in the cloud:
General design principles
Pillar-specific design principles
Enable traceability:
Log and audit all actions and changes to your environment.

General Design Principles
Stop guessing your capacity needs
Test systems at production scale
Automate to make architectural experimentation easier
Allow for evolutionary architectures
Build data-driven architectures
Improve through game days

Questions
Pillar Area
Question Text
Question Context
Best Practices

Example Walkthrough

Introduction to the Company
Mappahood Corporation
Founded in 2008 by Ivor Terrene
Selling 3D Printed Cityscapes (B2B/B2C)
About to apply for investment
Have asked you to perform a review
of their platform as part of their due diligence
Cloud native
“Cityscapes you can stand over”

Mappahood Corporation: “Cityscapes you can stand over”

Introduction to the Company “Cityscapes you can stand over”
The company has three main departments:
Fly & Snap: image acquisition, preprocessing, and storage
Show & Sell: promoting, selling, and working with customers
Make & Ship: manufacture of products and delivery
Their architecture reflects Conway’s law:
“organizations which design systems ... are constrained to produce designs which
are copies of the communication structures of these organizations”
https://en.wikipedia.org/wiki/Conway's_law

Mappahood Corporation: “Cityscapes you can stand over”

• Work through the questions in the review
• Use the questions as a prompt
• In which places does this question apply?
• CURRENT STATE – what is being done now?
• FUTURE STATE – what do you think they should be
doing?
• Not an absolute right or wrong – use case specific
• It’s a guide to aid the review
• Maybe follow-up questions..

Upload: FTP Upload: SSH FTP
• Work through the questions in the review
• Use the questions as a prompt
• In which places does this question apply?
• CURRENT STATE – what is being done now?
• FUTURE STATE – what do you think they should be
doing?
• Not an absolute right or wrong – use case specific
• It’s a guide to aid the review
• Maybe follow-up questions..

Security

Security
The ability to protect information, systems, and assets
while delivering business value through risk assessments
and mitigation strategies.
Identity and access management
Detective controls
Infrastructure protection
Data protection
Incident response

Design Principles
Apply security at all layers
Enable traceability
Implement a principle of least privilege
Focus on securing your system
Automate security best practices

Key Services for Security IAM
Areas Key Services
Identity and Access
Management
Detective Controls
Infrastructure Protection
Data Protection
Incident Response
Elastic Load
Balancing
Amazon EBS Amazon S3 Amazon RDS
AWS Key
Management Service
MFA Token
Amazon VPC
AWS CloudTrail AWS Config Amazon CloudWatch
IAM
IAM AWS CloudFormation

Review: Security Pillar

Breakout

Breakout Timing
Pick team name (1 minute)
Review 3 questions (15 minutes)
 SEC 1
 SEC 4
 SEC 12
Agree on top change
Select presenter
If you need help, raise your hand!

Security: Key Issues Identified
The ability to protect information, systems, and assets
while delivering business value through risk assessments
and mitigation strategies.
Identity and access management: IAM
Detective controls: Logging & monitoring
Infrastructure protection: Security groups
Data protection: Data at rest and in transit
Incident response: Clean room

Reliability

Reliability
The ability of a system to recover from infrastructure or
service failures, dynamically acquire computing resources
to meet demand, and mitigate disruptions such as
misconfigurations or transient network issues.
Foundations
Change management
Failure management

Design Principles – Reliability
Test recovery procedures
Automatically recover from failure
Scale horizontally to increase aggregate system availability
Stop guessing capacity
Manage change in automation

Key Services for Reliability
Areas Key Services
Foundations
Change management
Failure management
IAM Amazon VPC
AWS CloudTrail AWS Config
AWS CloudFormation
Amazon CloudWatch

Review: Reliability Pillar

Breakout

Breakout Timing
 REL 2
 REL 5
 REL 7
Agree on top change

Reliability: Key Issues Identified
The ability of a system to recover from infrastructure or
service failures, dynamically acquire computing resources
to meet demand, and mitigate disruptions such as
misconfigurations or transient network issues.
Foundations: Plan Amazon VPC
Change management: Auto Scaling
Failure management: Multi-AZ

Performance Efficiency

Performance Efficiency
The ability to use computing resources efficiently to meet
system requirements, and to maintain that efficiency as
demand changes and technologies evolve.
Selection
Review
Monitoring
Trade-off

Design Principles
Democratize advanced technologies
Go global in minutes
Use serverless architectures
Experiment more often
Mechanical sympathy

Key Services for Performance Efficiency
Areas Key Services
Selection (Compute,
Storage, Database,
Network)
Review
Monitoring
Trade-Off
Amazon EBS Amazon S3 Amazon RDSAuto Scaling Amazon Glacier
Amazon
CloudFront
Amazon
DynamoDB
Amazon
CloudWatch AWS Lambda
Amazon ElastiCache AWSSnowball
AWS
CloudFormation AWS Blog
Amazon CloudWatch

Review: Performance
Efficiency Pillar

Breakout

Breakout Timing
 PERF 1
 PERF 2
 PERF 4
Agree on top change

Performance Efficiency: Key Issues Identified
The ability to use computing resources efficiently to meet
system requirements, and to maintain that efficiency as
demand changes and technologies evolve.
Selection: Functions instead of Instances
Review: Newer instance types
Monitor: Metrics
Trade-off: Amazon CloudFront

Cost Optimization

Cost Optimization
The ability to avoid or eliminate unneeded cost or
suboptimal resources.
Cost-effective resources
Matched supply and demand
Expenditure awareness
Optimizing over time

Design Principles
Adopt a consumption model
Benefit from economies of scale
Stop spending money on data center operations
Analyze and attribute expenditure
Use managed services to reduce cost of ownership

Key Services for Cost Optimization
Areas Key Services
Cost-effective resources
Matched supply and demand
Expenditure awareness
Optimizing over time
Amazon CloudWatch
Auto Scaling
Amazon SNS
Reserved Instances AWS Trusted Advisor
AWS Blog & What’s New
Cost Allocation Tags

Review: Cost Optimization
Pillar

Breakout

Breakout Timing
 COST 1
 COST 5
 COST 6
Agree on top change

Cost Optimization: Key Issues Identified
The ability to avoid or eliminate unneeded cost or
suboptimal resources.
Matched supply and demand: Amazon CloudWatch
Cost-effective resources: Upload to Amazon S3
Expenditure awareness: Monitoring
Optimizing over time: AWS Lambda

Operational Excellence

Operational Excellence
The ability to run and monitor systems to deliver
business value and continually improve supporting
processes and procedures.
Preparation
Operations
Responses

Design Principles
Perform operations with code
Align operations processes to business objectives
Make regular, small, incremental changes
Test for responses to unexpected events
Learn from operational events and failures
Keep operations procedures current

Key Services for Operational Excellence
Areas Key Services
Preparation
Operations
Responses
AWS
CloudTrail
AWS
Config
AWS
CloudFormation
Amazon
CloudWatch
Amazon
CloudWatch
AWS
CloudFormation
AWS
CloudFormation
Lambda
RunCommand
AWS Batch
Lambda
RunCommand
AWS Batch
Lambda
RunCommand
AWS Batch
AWS
Config
AWS
Config
AWS
Developer
Tools
AWS
CloudFormation
AWS
CloudTrail
AWS
Developer
Tools
AWS
Developer
Tools

Review: Operational
Excellence Pillar

Breakout

Breakout Timing
 OPS 2
 OPS 4
 OPS 5
Agree on top change

Operational Excellence: Key Issues Identified
The ability to run and monitor systems to deliver
business value and continually improve supporting
processes and procedures.
Preparation: Make Operations Decisions Up Front
Operations: Release Management and Service Execution
Responses: Managing Incidents (RCA) and Optimization

Review Wrap-Up

Review Wrap-Up
Review:
Common areas identified
Critical issues missed
Well-Architected:
Definition
Trade-offs
Continuous improvement
Guidance

Example Issues by Pillar
Security Reliability Performance
Efficiency
Cost
Optimization
Operational
Excellence

Summary: Purpose of Well-Architected
Strategies & best practices for architecting in the cloud
Questions allow you to measure your architecture against best
practices and how to address any shortcomings
Making informed decisions about architecture in the cloud
Questions are the starting point
Not a binary “yes” or “no”
Consistency of reviews

Available Resources
AWS Well-Architected Framework Whitepaper
Pillar-specific Whitepapers
 Prescriptive, high-level implementation guidance
Free online training
https://aws.amazon.com/well-architected

Available Resources
Best practices can be
found in the AWS Well-
Architected Framework
Whitepaper:

Remember to complete
your evaluations!

Thank you!

© 2017 Amazon Web Services, Inc. or its affiliates. All rights reserved.
This work may not be reproduced or redistributed, in whole or in part, without
prior written permission from Amazon Web Services, Inc. Commercial
copying, lending, or selling is prohibited.
Errors or corrections? Email us at aws-course-feedback@amazon.com.
Other questions? Contact us at
https://aws.amazon.com/contact-us/aws-training/.
All trademarks are the property of their owners.
aws-well-architected@amazon.com

WKS402A Well-Architected Workshop

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Similar a WKS402A Well-Architected Workshop

Similar a WKS402A Well-Architected Workshop (20)

Más de Amazon Web Services

Más de Amazon Web Services (20)

Último

Último (20)

WKS402A Well-Architected Workshop