Are you Well Architected?

© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Are You Well-Architected?
Fitz (Philip Fitzsimons)

When you look at the system your team
is building, can you answer the question:
“Are you Well-Architected?”

Are you Well-Architected?
Security Reliability
Performance
efficiency
Cost
optimization
Operations

Are you Well-Architected?
Performance
efficiency
Cost
optimizationOperations
Review
process
Consistent Technology
portfolio

https://aws.amazon.com/well-architected/
AWS Well-Architected

History
Well-Architected
started
2012
Questions across
four pillars
2014
Operational
excellence
2016
Well-Architected
Tool
2018
AWS SA reviews
2013
Published framework
2015
APN partners, lens
2017 2019

© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Amazon Confidential
Why AWS
Well-Architected
Framework?
Learn AWS best practices
Build and deploy faster
Lower or mitigate risks
Make informed decisions

A mechanism for your cloud journey
Learn Measure Improve

What is the AWS Well-Architected Framework?
Design principles QuestionsPillars

Pillars of AWS Well-Architected
Performance
efficiency
Cost
optimization
Operational
Excellence

Intent of review
Working together
to improve
Not an audit
Throughout
lifecycle
Not a one-time check
Pragmatic,
proven advice
Not architecture astronauts

AWS Solutions
Architect
AWS
APN partner
AWS
WA tool
Your team technical
and business leads
Self-service
Partner
AWS SA
Review choice

Partner Well-Architected reviews
Results including
Statement of Work (SoW)
for improvements
Approve SoW within
30 days receive $5k
in AWS credits
Engage with a
Well-Architected partner
for a free review
https://aws.amazon.com/architecture/well-architected/partners/

Containers focussed
AWS and DevOps
consultancy and
Next-generation MSP

There are more than 20
billion connected devices
today.
Less than 1% of 1% of us
can understand and
influence them.
Kano believes in a future
where anyone can.

“As we hit a period of growth and are on the cusp of the change from Startup to Scaleup we
took a moment to pause and put our AWS estate in order
(Russell Ormes, Principal Engineer, Kano computing)

“As we hit a period of growth and are on the cusp of the change from Startup to Scaleup we
took a moment to pause and put our AWS estate in order, and
that’s how we got to Steamhaus … their impact has been wholly positive. Their openness
about the decisions they make not only inspires confidence in the platform … but allows us to
learn and take ownership of our infrastructure at whatever level we are comfortable with. This
fits well with our core mission to demystify technology for everyone, even ourselves.”

95% increase IN unique active
users across all the Kano
products from 2017 to 2018

Security Reliability Performance
Efficiency
Cost
Optimization
Operational
Excellence
Unified approach
• Automate
• Remove risk
• Speed up delivery
• Onboard staff
Move from manual
provisioning to
managed services
ease management of
security and
authentication
• K8S inherits IAM
policies. EKS uses
IAM for Cluster
authentication
Istio for egress filtering
and mutual TLS
between workloads
K8S scheduler ensures
required number of
workload replicas are
present, healthy and
scale in line with
demand
Automated termination
and replacement of
unhealthy pods
ability to scale more
fluidly and rapidly due
to inheriting the
benefits of lightweight
containers.
Bootstrapping is
minimal or non-existent
K8S on EKS enables
higher infrastructure
density and less
wastage.
Current estimate of
cost saving from this is
20% to 30%.
use of RIs expected to
achieve ~15% saving

“we are excited to see where this journey will take us
and Steamhaus is helping us pave the way for a more
efficient journey.”

Stand b16
@Steamhausmcr
hello@Steamhaus.co.uk

Learnings
Earlier
is better
Pre-launch only?
Not considered
decisions
Make bad decisions?
Most workloads
can be improved
Findings?

Use cases
Portfolio
management
Technology
governance
Learning best practices
for the cloud

S U M M I T © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Performance
efficiency
Cost
optimization
Operations

OE: Planes of operations
Control Plane Data Plane
Management Plane

Management Plane
Manage a resource Talk to resource
Configure the service

Management Plane
Manage a resource Talk to resource
Configure the service
The code you write for operations is the
operations plane for that system. It should
be written to the same (if not higher)
engineering discipline as the other planes

SEC: Improving Responses
Write Playbook (p=process, markdown)
Page security team, contact AWS support
Isolate instance (remove security groups)
Isolate IAM entities with explicit deny policies
Forensics: Persistence?, Snapshot EBS, Flowlogs
Game day (org. muscle memory, refinement)
Write Runbook (r=routine, script)
CloudWatch Events for anomalies

REL: Recovery oriented computing
a a a

a a a
x
a aa

a a a
x
a aa
x
x
Un-tested paths will fail. Game days.

PERF: Deming Cycle (PDCA)
(start)
Plan – what achieve?
Do – execute the plan
Check – study the results
Act – make improvements
(repeat)

PERF: Deming Cycle (PDCA)
(start)
Plan – what achieve? Reduce time
Do – execute the plan Update CloudFormation
Check – study the results Was it a positive improvement?
Act – make improvements Merge into mainline
(repeat)

COST: Doing more with less
Who has had formal training in IT?
Did that training cover security?
Did it cover cost?
Have you ever reduced cost after launch?
Ever used those savings to do more?
Measure value being delivered vs. cost of delivery

Well-Architected Labs
https://github.com/awslabs/aws-well-architected-labs

Getting started
https://aws.amazon.com/well-architected/
Review first workloadAccount team or partnerRead online resources

Are you Well Architected?

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Are you Well Architected?

Similar to Are you Well Architected? (20)

More from Amazon Web Services

More from Amazon Web Services (20)

Are you Well Architected?