• Save
Perform a Cloud Readiness Assessment for Your Own Company
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Perform a Cloud Readiness Assessment for Your Own Company

  • 759 views
Uploaded on

In this session you will get an understanding how to evaluate your company's or applications' cloud readiness. We will cover aspects such as workload and data categorisation, automation levels,......

In this session you will get an understanding how to evaluate your company's or applications' cloud readiness. We will cover aspects such as workload and data categorisation, automation levels, design for failure and cost-optimised architectures. We will be looking at typical application evolution paths from tightly coupled physical systems, in some cases through virtualisation, to cloud-native, or cloud-ready, loosely coupled, distributed and automated solutions.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
759
On Slideshare
759
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
2

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Assessing Your Company’s Cloud Readiness
  • 2. Why? What? How?
  • 3. Why? What? How?
  • 4. There are many reasons to move to the Cloud #1: Agility #2: Platform Breadth #3: Continual Iteration and Innovation Our 44th Price Reduction ü #4: Cost Savings and Flexibility
  • 5. There are many ways to move to the Cloud #1: Development and Test #2: New Workloads #3 Supplement existing workloads #4: Integrate Cloud Workloads with Existing On-premises systems #5: Migrate Existing Applications #6 DC Migrations and All-In
  • 6. Why? What? How?
  • 7. Strategy & Business Goals
  • 8. Cloud Strategy – Business Goals Alignment Topline Efficiency
  • 9. Cloud – Tool or Competitive Advantage? Cloud-first Strategy? Strategic Investment?
  • 10. Applications
  • 11. Application Architecture Monolithic & static, Tightly coupled, Specific & dedicated (v)HW BoM, Design for Failover, Stateful, Scale up EBS, S3, RDS, ELB, Cloudwatch.. Monolithic SW, Leveraging Infrastructure Services SOA & Microservices, Loosely coupled, Adaptive, Design for Failure, Stateless, Scale out
  • 12. Cloud SOA & Microservices Separate services Exposed via API Scale, assure separately Buy Commercial SW Build Develop in-house Own skills & IP Open Source Fully open source In-house support Open Source + + Enterprise Support e.g. Red Hat
  • 13. Processes
  • 14. R&D Processes Rare Release Events “Waterfall Methodology” Frequent Release Events “Agile Methodology” Smaller Effort “Minimized Risk” Larger Effort “Increased Risk” Time Change Time Change
  • 15. test plan code build Continuous Integration Agile Development Source http://www.collab.net deploy operate collaboration value DevOps release Continuous Delivery
  • 16. Data Value Strategy
  • 17. Data Value Strategy
  • 18. State of Data
  • 19. Map Data Sources Customer-facing Applications? Internal Systems? External – Social / Open / Commercial Feeds?
  • 20. Data Sources Have already? Initial Data Set Being Generated? Fresh Data Throwing Away? Ignored
  • 21. Storage Single source of truth? Durability? Capacity? Cost?
  • 22. S3 as a “single source of truth” S3 Courtesy http://techblog.netflix.com/2013/01/hadoop-platform-as-service-in-cloud.html
  • 23. Data Quality Control Control Data Correct Data Validate Data Enrich Data
  • 24. Data Value Strategy – Business Goals Alignment Time to Result Cost of Result
  • 25. Data Value Add
  • 26. Data Exposure – via API Internal Partners Customers Ecosystem
  • 27. Why? What? How?
  • 28. What will you need for the Journey? You’ll need a reason You’ll need tools You’ll need a map • AWS Team • Partners (SIs, Niche, MSP, etc) • Training • Enterprise Support model You’ll need a guide • Discovery and Assessment Process defining the roadmap, quick wins and adoption plan • TCO analysis and business case • Business benefits and value analysis • Cost of migration and execution plan • Technology assessment • Security assessment • Portfolio evaluation • Technology partners
  • 29. What will you need for the Journey? You’ll need a reason You’ll need tools You’ll need a map • AWS Team • Partners (SIs, Niche, MSP, etc) • Training • Enterprise Support model You’ll need a guide • Discovery and Assessment Process defining the roadmap, quick wins and adoption plan • TCO analysis and business case • Business benefits and value analysis • Cost of migration and execution plan • Technology assessment • Security assessment • Portfolio evaluation • Technology partners
  • 30. AWS Enterprise Engagement Model • All resources are based in APAC – local to you • Connections with the product teams • Executive relationship with customers • Support during all phases of your journey to the Cloud AWS Enterprise Engagement Model YOU Account Manager (Customer) Solution Architect Enterprise Support Partner(s) (Sis, ISVs) Prof. services Training and Certification
  • 31. AWS Training & Certification Certification Demonstrate your skills, knowledge, and expertise with the AWS platform aws.amazon.com/certification Self-Paced Labs Try products, gain new skills, and get hands-on practice working with AWS technologies aws.amazon.com/training/ self-paced-labs Training Skill up and gain confidence to design, develop, deploy and manage your applications on AWS aws.amazon.com/training
  • 32. Worldwide Training Partners Visit aws.amazon.com/partners/overview/training-partner/
  • 33. AWS Partners focusing on Migrations Let’s talk a little bit about the ecosystem…
  • 34. What is AWS Enterprise Support? • 24x7 support model • Dedicated Technical Account Manager • A range of plans for every customer size and scale • Unlimited number of support cases • Pay-by-the-month pricing • No long-term commitments • Additional support for • Customer event management • Cost optimisation for the AWS resources
  • 35. What will you need for the Journey? You’ll need a reason You’ll need tools You’ll need a map • AWS Team • Partners (SIs, Niche, MSP, etc) • Training • Enterprise Support model You’ll need a guide • Discovery and Assessment Process defining the roadmap, quick wins and adoption plan • TCO analysis and business case • Business benefits and value analysis • Cost of migration and execution plan • Technology assessment • Security assessment • Portfolio evaluation • Technology partners
  • 36. What will you need for the Journey? You’ll need a reason You’ll need tools You’ll need a map • AWS Team • Partners (SIs, Niche, MSP, etc) • Training • Enterprise Support model You’ll need a guide • Discovery and Assessment Process defining the roadmap, quick wins and adoption plan • TCO analysis and business case • Business benefits and value analysis • Cost of migration and execution plan • Technology assessment • Security assessment • Portfolio evaluation • Technology partners
  • 37. Cloud Adoption: an iterative process Joint Discovery Workshop (find suitable workload) Live Supported System or POC IT Transformation with AWS Partners and Professional Services Technical Design with AWS Solution Architects Support & Operations with AWS Enterprise Support TAM Training & Certification with AWS Training Stakeholder Sponsorship Stakeholder Review Repeat
  • 38. Discovery Workshop Business Level Technical Level IT Operations Discovery Workshop Results Context • Industry Insights • Business Strategies and Priorities • Capabilities and benefits Analyse • Assess Current State • Define Future State • Identify quick wins and blockers Prioritize • Select and Rank Initiatives • Create a roadmap • Build evaluation plan AWS Awareness Design Framework and Roadmap Business case and value Technology evaluation and POC STRATEGIC ASSESMENT
  • 39. What will you need for the Journey? You’ll need a reason You’ll need tools You’ll need a map • AWS Team • Partners (SIs, Niche, MSP, etc) • Training • Enterprise Support model You’ll need a guide • Discovery and Assessment Process defining the roadmap, quick wins and adoption plan • TCO analysis and business case • Business benefits and value analysis • Cost of migration and execution plan • Technology assessment • Security assessment • Portfolio evaluation • Technology partners
  • 40. What will you need for the Journey? You’ll need a reason You’ll need tools You’ll need a map • AWS Team • Partners (SIs, Niche, MSP, etc) • Training • Enterprise Support model You’ll need a guide • Discovery and Assessment Process defining the roadmap, quick wins and adoption plan • TCO analysis and business case • Business benefits and value analysis • Cost of migration and execution plan • Technology assessment • Security assessment • Portfolio evaluation • Technology partners
  • 41. The Journey to Big Business Results Current State Future State High up front costs – high risk Low up front costs – easy experimentation Expensive to get, keep secure Security and certification built-in Long time to value Agility enabling quick wins Local first then add regional Going global instantly Focus on maintenance Focusing on core business
  • 42. The Journey Brings Fast Learning & Early Wins Explore Adopt Expand Transform Non- Production Existing Web Workloads New Capability Workloads Legacy Migration
  • 43. Migration process: collect information, assess the portfolio and decide on migration • Collect information on the applications • Assess applications against migration criteria • Decide which applications should be migrated, when and how (as well as the data required by the applications) Assessment is part of the practice of Application Portfolio Management.
  • 44. Essential attributes for the migration analysis (1 / 3 ) Section Attribute Reason General Information Type of license Software licenses for applications may have to be moved to the cloud. AWS supports licensing options for major COTS applications. Lifecycle stage Is the application due for retirement or replacement? If so, it may not need to be migrated. Business value Cost reduction Does the application support efficiency and cost reduction targets? If so, it should be given special attention in the migration. Impact on revenue and market share Does the application support revenue generation and market share? If so, it should be given special attention in the migration. Usage The number of users and how often they use the application affects its importance. Applications used only by a few users or infrequently may not justify enhancement effort in the migration. SLAs SLA targets and past data will provide indications on reliability and supportability on premises. High SLA applications will need to be migrated to suitable architectures on the cloud and may need more effort.
  • 45. Essential attributes for the migration analysis (2 / 3) Section Attribute Reason Financials Enhancement cost A high cost of enhancing an application may justify migrating it to AWS and enhancing using the Embrace or Optimise strategies. Replacement cost A low cost of replacing an application may justify replacing it so it does not need to be migrated. Licensing costs A high cost of software licensing may justify considering lower cost options as part of the migration to AWS from a cost benefit aspect. Security, privacy and compliance Security of applications and data The security requirements need to be known so they can be catered for on AWS through appropriate architecture and operational processes. Data privacy The data privacy requirements need to be known so they can be catered for on AWS through appropriate architecture and operational processes. Obligations to store data in specific jurisdictions Regulatory and other constraints need to be known and may disallow some applications from moving to AWS.
  • 46. Essential attributes for the migration analysis (3 / 3) Section Attribute Reason Dependencies Applications that this application depends on Dependencies between applications on-premises must be known. The assessment of inter-dependent applications must take into account the interfaces between them and how the interfaces should be implemented on AWS. A hybrid arrangement is possible with parts of an application running both on-premises and on AWS but this is more complex to implement. Other applications that depend on this application Risks Operational risks. Are there existing operational risks with the application? If so, it may be best to defer migrating until they have been resolved. Technical qualities (Varies by type of application) Are there any technical quality attributes listed in the paper that affect the potential for migration? Application environment CPU Does the application run on the x86 family of CPUs supported by AWS? If not, re-targeting will be needed, where feasible. OS Does the application run on the operating systems supported by AWS? If not, re-targeting will be needed, where feasible.
  • 47. Options for Migrating Applications to AWS • Migrated without change (Forklift or ‘Lift-and-Shift’) – Map on-premises technology services to AWS services – Does not provide the full benefit of AWS but less effort is needed • Migrated with some improvements (Embrace AWS) – Full re-development is not justified but specific AWS services are used – Provides more benefits with more effort • Migrated by re-architecting and re-developing (Optimise for AWS) – Re-architecting and re-developing is justified – Can provide full benefits but needs the most effort
  • 48. The Journey Has Parallel Paths Explore Adopt Expand Transform Enterprise Apps (e.g. SAP) Demos and Training Multiple Environments of Dev & Test Sandboxes and Departmental Core Enterprise Production Departmental LOB Apps New Business Capabilities Existing Business Capabilities Variable Load Transactional Apps Steady Load Integrated Workflow Apps Business Intelligence and Analytics New Data and Compute Intensive Projects Analytics Extensions (warehousing, big data, etc.) Multi-source Data Lake for Collaboration Service Enabled Master Data Management Web and Mobile Applications New Variable Load Web Apps Existing Variable Load Web Apps Customer-facing Web and Mobile at Scale Web and Mobile Integrated Across the Business Operations and Service Delivery Dev & Test (Dynamic Utilization) Backup and Archive Storage Life Cycle Disaster Recovery and Business Continuity Full Cloud ITSM for Entire Service Catalog
  • 49. Understanding Modern IT Operating Model Environments Assets Monitoring Metering Events & Alerts Identity Metering & Billing Events & Alerts Existing IT Environment Presentation Service Desk Service Portal APIs Service Integration Service Management Operations Management Governance Service Catalog IT Standards Policies Principles Templates Definitions Patterns Constraints How? Runbook Repository Known States CMDB Metrics Financials Reports Analysis What? Operations Data Warehouse Assets Monitoring AWS APIs CloudWatch Detailed Billing CloudTrail IAM AWS Environment Identity Modern IT Operating Model
  • 50. Summary • Transition to the Cloud is a journey which needs to be planned and managed – Destination includes a New Operating Model for the Enterprise – Lead the Change – Business Opportunity, Not Just Technology • AWS team has people, process and technology platform to transition you to the Cloud and support you there – Partners Can Help Deliver Results Faster • Talk to your AWS Account team about the Cloud Discovery workshop - a great place to start your Cloud Adoption planning
  • 51. Follow us on at @AWSCloudSEAsia Join the AWS User Group at Facebook.com – search ‘AWS User Group Singapore’
  • 52. Thank you