The document discusses considerations for organizations embarking on a cloud journey. It outlines four stages of cloud adoption: Project, Foundation, Migration, and Optimization & Reinvention. Organizations that accelerate their adoption realize value earlier. The AWS Cloud Adoption Framework (CAF) introduces six perspectives to help develop a structured approach: business, people, governance, platform, security, and operations. The CAF can help align cloud strategy to business outcomes and execute initiatives to realize desired outcomes through a successful cloud journey.
4. Cloud stages of adoption
Organizations typically follow a four-stage path as they adopt
cloud with additional value being delivered by each stage.
Project
Foundation
Migration
Value
Time
Optimisation &
Reinvention
5. Setting your path
If organizations can accelerate adoption, they realize greater value
earlier in the journey and help foster greater innovation.
RETIRE TECHNICAL DEBT
FOSTER INNOVATION
Value
Time
Project
Foundation
Migration
Optimisation &
Reinvention
6. Without a solid foundation
…organizations will fail to realize the benefits of cloud.
Migration
Value
Time
THE GREAT STALL
Optimisation &
Reinvention
MISSED
OPPORTUNITY
Project
Foundation
7. Why do organizations stall?
More often due to organizational constraints
• Absence of Executive management support
• Inexperience with complex change/transformation
• Reasonable expectations for timelines and budget requirements
• Lack of defined roadmap and strategic goals for cloud
• Lack of procurement vehicle and acquisition mechanisms
• Internal politics
• Gaps in Human resource support
• Incompatible culture
… as opposed to technical ones
9. Agenda
Starting your cloud journey
Cloud Adoption Framework and
perspectives
Path to reinvention
10. AWS Cloud Adoption Framework (CAF) value
Building a comprehensive approach to cloud
1. Align cloud strategy to business
outcomes
2. Deliver results through new cloud skills
and experiences
3. Execute your cloud initiatives
4. Realize your desired business outcomes
13. When considering adoption of AWS, many
of our customers focus solely on the
opportunities to reduce costs without
considering the wider business benefits a
move to the cloud could bring.
14. • Capex ↓↓
• Opex ↓↓
• Opportunity cost ↓↓
• Risk premium ↓↓
• Revenues ↑↑
• Time saved ↑↑
• Support overhead ↓↓
• MA&D time ↓↓
• Defects ↓↓
• Outages ↓↓
• Security ↑↑
• User satisfaction
↑↑
• Cycle times ↓↓
• POC delivery ↓↓
• Innovation ↑↑
• Speed to market ↑↑
• Complexity ↓↓
Understanding value benefits
Cost savings Resource efficiency Operational resilience Business agility
16. Cultural trends we are seeing
Moving from
Failure is not an option
Command and control
Silos “throw it over the wall”
Build/deploy in place
Long due diligence
Standardization
Talent outsourcing
Moving toward
Learning (start small, experiment, and iterate)
Decentralized ownership (guardrails via Cloud CoE)
DevOps and cross-functional teams
Automate: Infra-as-code, redeploy every time
Adopt early and often
Reference architecture, no religion, few standards
Talent insourcing/niche partnering
17. CCoE is a team of open-minded change agents,
tasked with initiating and implementing a
fundamental shift in how the organization functions
The team should evolve as a business progresses
through the stages of cloud adoption
Diverse and cross functional
representation is key
Big picture thinkers who are ready to lead business
transformation
Cultural change via a cloud center of excellence
18. AWS approach to organizational change
1
2 3
4
5
6
Mobilize
team
Align
leadership
Envision
the future
Engage the
organization
Enable
capacity
Make
it stick
Articulate cloud vision,
build commitment, and
establish communication channels
Align organization, institutionalize
new operating model, and
transition to the cloud
Confirm sponsorship,
secure resources, and
build momentum
20. Governance
Governance encompasses an organization’s mission, long-
term goals, responsibilities, and decision making.
At the most abstract level, governance seeks to ensure that
what we are governing is doing the right things right:
Are we doing the right things?
Are we doing them the right way?
How do we know?
23. Innovation Migration
Driving new customer
engagement opportunities
Launching prototypes
Creating new business value
Moving legacy
applications to the cloud
Updating best practices
Standardizing workloads
Unlocking value from your cloud journey
24. We do not claim this is the “right” way to
organize for innovation. This is what we’ve
adopted and works for us:
start with the customer
and work backwards.
Build a culture of innovation
Faster innovation cycles Faster, deeper insights AI
28. Customer
AWS is responsible for
security of the cloud
Customer is responsible for
security in the cloud
Customer data
Platform, applications, identity, and access management
Operating system, network, and firewall configuration
Client-side data encryption and
data integrity authentication
Server-side encryption
(file system and/or data)
Network traffic protection
(encryption/integrity/identity)
Compute Storage Database Networking
Edge
locations
Regions
Availability zones
AWS Global
Infrastructure
AWS Shared Responsibility Model
AWS
29. Security best practices
Implement a strong identity foundation
Enable traceability
Automate security best practices
Protect data in transit and rest
Prepare for security events
Apply security at all layers
31. “Are we ready to support
production applications on AWS?”
32. What “good” operations looks like
Security built into
the DNA
Guardrails not
blockers
Flexibility – one size
doesn’t fit all
Automation – accounts,
ops, IR, remediation
Centralized governance, decentralized
implementation
Consistent and repeatable
Infrastructure as Code
33. Agenda
Starting your cloud journey
Cloud Adoption Framework and
perspectives
Path to reinvention
35. AWS CAF perspectives and executing each step
Applying the framework to drive cloud adoption
Envision
Clarify business outcomes and
align with organizational goals
Define measurable success
criteria (metrics)
Demonstrate how technology
will enable business outcomes
Alignment
Identify critical-to-success
stakeholders
Foster stakeholder consensus
and alignment
Understand how stakeholders will
benefit from cloud
Create a comprehensive
action plan
Launch
Execute your cloud projects
Start the incremental business
value of leveraging the cloud
Proactively address stakeholders’
questions, concerns, and blockers
Realize value
Recognize ongoing incremental
business value
Continually evaluate cloud strategy
and align with envisioned outcomes
Identify additional cloud projects
that deliver value
1 2
3 4
2
34
1
36. Next steps
Broaden stakeholder engagement
Deepen your understanding of cloud
Focus on developing your new culture
…start building