"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...
Aberdeen Oil & Gas Event - Cloud Adoption Framework
1. ENABLEMENT AND EXECUTION: “HOW WE HAVE SEEN COMPANIES ADOPTING AWS”
AND WHAT WE HAVE LEARNT… AN INTRODUCTION TO THE CLOUD ADOPTION FRAMEWORK
2. Objectives
What’s the Cloud Adoption Framework (CAF)
•1 deep dive
•There is major disruption
3. The journey we’re seeing with AWS
customers
Dev & Test True Production Mission Critical All-in
Build production apps
Migrate production apps
Marketing
Build mission-critical apps
Migrate mission-critical apps
Development and
test environments
Corporate standard
4. PlanBuildOperate
Governance
Management
Competencies
Business Strategy
Information Technology Strategy
Architecture
Transition to Operations
Innovate
Continuously Improve
Iterate
Evolve
Initiate IT Project
Every Company has a unique adoption journey
5. But, there are basic questions on the journey
What skills and capabilities are required? How to compose migration team?
How to structure cloud programs? How to ensure quality of delivery?
Customers are asking us for the high-level enterprise-wide organizing logic for mapping their business needs to IT capabilities, reflecting the agility, integration and standardization changes that cloud computing brought to IT industry.
Strategic relationships are opening- up new set of questions, requiring AWS to demonstrate delivery capability, technology insight, and practical business value to our customers.
Will risk increase?
Can we run cloud secure and compliant?
What are the priorities? When to deliver solutions?
How to design foundations? How to migrate workloads?
What are key ops capabilities? What is the new ITSM cycle?
Why to invest? Why change?
How to measure success?
The AWS CAF organizes and describesthe perspectives in planning, creating, managing, and supporting a modern IT service.
Offers practical guidance and comprehensive guidelines for establishing, developing and running AWS cloud-enabled environments.
It provides a structurewhere business and IT can work together towards common strategy and vision, supported by modern IT automation and process optimization.
People
Perspective
Process
Perspective
Security
Perspective
Maturity
Perspective
Platform
Perspective
Operating
Perspective
Business
Perspective
6. Sample IT Adoption Roadmap
Discovery Workshop
Cloud Business Case
Define Security Requirements
Define Network Environment
Define Governance Structure
Operational Integration
Security Operations Playbook
Cloud Environment Optimization
Application PortfolioAnalysis
Cost and Billing Analysis
Training and Certification
Define Cloud Environments
Define EA Policies and Practices
7. Objectives
What’s the Cloud Adoption Framework (CAF)
1 deep dive
•There is major disruption
8. Maturity Perspective
CAF Maturity Perspective
Maturity model helps customers with structured, systematic assessment and planning of capability maturity, defining the most optimal map towards effective use of cloud computing.
Focus of maturity perspective components is on consistent implementation towards more secure, well-managed and cost-optimized cloud-based IT capabilities.
Cloud Readiness Assessment
Cloud Maturity Heat-map Assessment
Target Platform Capabilities
Application PortfolioAnalysis
Roadmap sequencing
IT Management Assessment
9. •Conduct application discovery workshop
•Interview application owners
•Implement tool-based discovery
•Profiling application inventory
•Identifying complexity, criticality and preferences
•Clustering and prioritizing
•Driven by prioritization, skills and best practices
•Use best patterns
•Capture inter- dependencies
•From “lift and shift” to “drop and shop”
•Expect complete IT transformation
•Include IT process changes and organizational change management
•Focus on new Operations model
Application portfolio assessment
Collecting application portfolio inventory
Defining segmentation and prioritization criteria
Determining application migration options
Creating application migration roadmap
10. •Semi-automated process with automation rate improving with experience
•Combination of AWS and partner tooling with best practices and custom questionnaires
•Requires light participation/ workshops with business application owners
•Ranking is specific for each customer/environment, but is based on standard AWS approach
Information collected:
•Name of the app, technical owner, business owner
•Number of systems: direct (exclusive), indirect (dependent), non-prod (dev-test)
•Infrastructure desc(network, ports/protocols, security, virtualizer, directory, OS)
•Information desc(database, data classification, data exchange)
•App desc(app framework, middleware used, web tier used, devlanguage)
Automation tools:
•RISC Network –CloudScape
•ScienceLogic–CloudMapper
•ServiceNow–Service Watch
•Blue Stripe -FactFinder
Application discovery and collection
11. Business criticality (frequency of use, size of user base, supported business process)
•Deriving consequence factor of failure
Technology complexity (dependencies, fragility, understandability of the app)
•Deriving probability of failure
Sizing (how many systems, data volumes, storage size, other volumetric requirements)
•Deriving effort of migration
HA/DR/BCP (continuity plans, availability requirements, backup/restore requirements)
•Deriving pre-and post-migration effort (cost of support and keeping the app current)
Segmentation and prioritization criteria
13. Discover/assess/prioritize
applications
Migration Tools
Transition
Production
Retain / not moving
Redesign application/
Infrastructure architecture
App code
development
Purchase COTS/
SaaS & licensing
Test
Modify underlying
infrastructure
Full ALM /
SDLC
Manual config
Manual deploy
Manual install
Retire / decommission
Determine
migration path
Automated
Manual install
& setup
Integration
Actual application migration patterns
14. Foundational Services
Cloud Platform –Modeling Canvas
Platform Services
Security
Firewall
Identity & Access
Auditing
Encryption
Storage
Object Store
File Store
Archiving
Backup/Recovery
Storage Integration
Compute
General Purpose
Compute optimized
Memory Optimized
GPU Optimized
Storage Optimized
Server OS
Linux
BSD
Windows
Other
Data Integration
ETL/ELT
Replication
Queueing
Data Load
MDM
App Services
Mobile
App Store
Push
Analytics
Identity
Composites
Search
Workflow
Messaging
Streaming
Transcoding
Orchestration
Protocols
http
REST
SMTP
IM/SMS
SOAP/WS-*
RDP/VNC
SSH
Clients
Browser
Email
Legacy App
Mobile App
TXT
Store app
Term
Data Analytics
Data streaming
Data Processing
Data Mining
Machine Learning
Event Processing
Networking
Cloud Isolation
Connectivity
Elasticity
Name Resolution
Content Delivery
App Server
Java
PHP
Python
Ruby
.NET
Node.js
SAP
Database
Relational
NoSQL
In-memory DB
Data Warehouse
HANA
16. Objectives
What’s the Cloud Adoption Framework (CAF)
1 deep dive
There is major disruption
17. Technology is easy!
BusinessCapabilities
Technology change is the easy part, the biggest challenges are on the other dimensions of a major adoption.
Cloud is disruptive in the industry, in the market, and on any program it s applied upon.
19. Application Migration Roadmap
Cloud Adoption Strategic Initiative
Launch and mobilize
Cloud Adoption –Service Analysis & Design
Maturity and Gap Analysis
Cloud Technology Foundation Design
IT Organization Redesign
IT Process Redesign
Application Portfolio Assessment
Cloud Adoption –Service Transition
Integrated IT Operating model
Provisioning, Migrations, Handover
Cloud Adoption –Service Operations
Monitoring, ITSM Management
SLA Management, Billing, Reporting
Cloud Adoption –Portfolio Governance
Weeks 1-4
Weeks 5-8
Weeks 9-12
Weeks 13-16
Weeks 17-20
Weeks 21-24
Weeks 25-28
Weeks 29+
Define Cloud Strategy & Team
20. Application Migration Team
Architecture team
Lead Architect
Migration team
Migration Lead
Operations team
CloudOperations Lead
PM Office
Head Scrum Master
Security Lead
Networking Lead
Foundation Lead
Cloud Ops -Network
Storage & DB Lead
Linux compute Lead
Windows compute Lead
Automation Lead
DevOpsLead
Project Manager
Web migration Lead
Linux app stack Lead
Win app stack Lead
Oracle DB Lead
Cloud Ops -Automation
Cloud Ops –Front-end
Cloud Tooling Lead
Cloud Ops –Middleware
Cloud Ops –Database
CIO Office
Cloud Program Lead
21. CAF Core Perspectives
ProcessPerspective
Managing portfolios, programs and projects to deliver expected business outcome on time and within budget, while keeping risks at acceptable levels.
PeoplePerspective
Defining and acquiring the skills neededto adopt the AWS cloud platform. Examples guidance include role descriptions, training, certification and mentoring.
MaturityPerspective
Defining the target state architecture of the organization and creating the required blueprints and roadmaps.
PlatformPerspective
Represents the technology services of the AWS cloud platform. Provides patterns, guidance, and tools for optimal use of the technology services and services to implement.
OperatingPerspective
Represents the ongoing management of the functioning IT environment of AWS. Provides process, guidance and tools for optimum operational service management of the AWS environment.
SecurityPerspective
Defining and implementing the required levels of security, governance, and risk management to achieve compliance.
BusinessPerspective
Identifying, delivering, and measuring business impact using architectural approaches that align technicaldelivery to business imperatives.
22. Takeaways
•Cloud adoption is a Journey
•A Migration requires a structured approach to assure consistent value realization
•Application migration is just a piece of large-scale Cloud Adoption, Do not over-analyze and over-design
•use optimization cycle to iterate
•The Cloud Adoption Framework helps you build the right “map”
Want more? The Cloud Adoption Framework whitepaper http://bit.ly/AWSCAF
