O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Considerations for your Cloud Journey

228 visualizações

Publicada em

Cloud adoption requires that fundamental changes are considered across the entire organization, and that stakeholders across all organizational units are engaged in these changes. This session will introduce participants to the AWS Cloud Adoption Framework (AWS CAF) to help organizations take an accelerated path to successful cloud adoption. Participants will be exposed to consideration, guidance, and best practices that can be used to help their organizations develop an efficient and effective plan to realize measurable business benefits from cloud adoption faster and with less risk.

  • Seja o primeiro a comentar

  • Seja a primeira pessoa a gostar disto

Considerations for your Cloud Journey

  1. 1. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Considerations for your Cloud Journey
  2. 2. Agenda Starting your cloud journey  Cloud Adoption Framework and perspectives  Path to reinvention
  3. 3. 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
  4. 4. 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
  5. 5. 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
  6. 6. 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
  7. 7. Value Time Project Foundation Migration Optimisation & Reinvention Cloud stages of adoption The AWS Cloud Adoption Framework (CAF) introduces six perspectives that helps organizations develop a structured approach to building a strong foundation and your cloud journey.
  8. 8. Agenda  Starting your cloud journey Cloud Adoption Framework and perspectives  Path to reinvention
  9. 9. 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
  10. 10. AWS CAF perspectives https://d1.awsstatic.com/whitepapers/aws_cloud_adoption_framework.pdf
  11. 11. Business perspective
  12. 12. 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.
  13. 13. • 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
  14. 14. People perspective
  15. 15. 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
  16. 16.  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
  17. 17. 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
  18. 18. Governance perspective
  19. 19. 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?
  20. 20. Guardrails • Code review • Authorization controls • Security testing • Separation of duties • Security monitoring • Audit trail • Security training
  21. 21. Platform perspective
  22. 22. 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
  23. 23. 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
  24. 24. Data center consolidation Acquisitions or divestitures Large scale compute intensive workloads Facility or real estate decisions Agility/dev productivity Cost reductionInnovation and digital transformation Colocation or outsourcing contract changes Common migration drivers © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
  25. 25. Why migrate? CORE SERVICES Integrated Networking Rules Engine Device Shadows Device SDKs Device Gateway Registry Local Compute Custom Model Training & Hosting Conversational Chatbots Virtual Desktops App Streaming Schema Conversion Image & Scene Recognition Sharing & Collaboration Exabyte-Scale Data Migration Text to Speech Corporate Email Application Migration Database Migration Regions Availability Zones Points of Presence Data Warehousing Business Intelligence Elasticsearch Hadoop/Spark Data Pipelines Streaming Data Collection ETL Streaming Data Analysis Interactive SQL Queries Queuing & Notifications Workflow Email Transcoding Deep Learning (Apache MXNet, TensorFlow, & others) Server MigrationCommunications MARKETPLACE Business Apps Business Intelligence DevOps Tools Security Networking StorageDatabases API Gateway Single Integrated Console Identity Sync Mobile Analytics Mobile App Testing Targeted Push Notifications One-clickApp Deployment DevOps Resource Management Application Lifecycle Management Containers Triggers Resource Templates Build & Test Analyze & Debug Identity Management Key Management & Storage Monitoring & Logs Configuration Compliance Web Application Firewall Assessment & Reporting Resource & Usage Auditing Access Control Account Grouping DDOS Protection TECHNICAL & BUSINESS SUPPORT Support Professional Services Optimization Guidance Partner Ecosystem Training & Certification Solutions Management Account Management Security & Billing Reports Personalized Dashboard Monitoring Manage Resources Data Integration Integrated Identity & Access Integrated Resource & Deployment Management Integrated Devices & Edge Systems Resource Templates Configuration Tracking Server Management Service Catalogue Search MIGRATIONHYBRID ARCHITECTUREENTERPRISE APPSMACHINE LEARNINGIoTMOBILE SERVICESDEV OPSANALYTICS APP SERVICES INFRASTRUCTURE SECURITY & COMPLIANCE MANAGEMENT TOOLS Compute VMs, Auto-scaling, Load Balancing, Containers, Virtual Private Servers, Batch Computing, Cloud Functions, Elastic GPUs, Edge Computing Storage Object, Blocks, File, Archivals, Import/Export, Exabyte-scale data transfer CDN Databases Relational, NoSQL, Caching, Migration, PostgreSQL compatible Networking VPC, DX, DNS Facial Recognition & Analysis Facial Search Patching Contact Center The world’s most valuable resource is no longer oil, but data. “ ”
  26. 26. Security perspective
  27. 27. 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
  28. 28. 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
  29. 29. Operations perspective
  30. 30. “Are we ready to support production applications on AWS?”
  31. 31. 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
  32. 32. Agenda  Starting your cloud journey  Cloud Adoption Framework and perspectives Path to reinvention
  33. 33. Elements of a successful journey
  34. 34. 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
  35. 35. Next steps  Broaden stakeholder engagement  Deepen your understanding of cloud  Focus on developing your new culture …start building
  36. 36. Thank you