5 Points to Consider - Enterprise Road Map to AWS Cloud

5,709
-1

Published on

This was presented by Supratik Ghatak, Co-Founder Blazeclan, at the AWS Summit Mumbai 2013. CIO pain points, cloud migration reasons and strategies are the key focus of this presentation. CIOs and CTOs can gain insights into various ways of leveraging the AWS cloud. The presentation also talks about the priority areas for CIOs & CTOs to look at while using the cloud as well as how to plan their strategies around AWS cloud. Further case studies are depicted that show how organization
can benefit from AWS Cloud.

Published in: Technology, Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
5,709
On Slideshare
0
From Embeds
0
Number of Embeds
15
Actions
Shares
0
Downloads
9
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

5 Points to Consider - Enterprise Road Map to AWS Cloud

  1. 1. Presenter NamePresenter TitleMonth Day, YearMigration Solution To Cloud
  2. 2. • 5% Organization Moved 50% Apps toCloud• 30% Moved to cloud based on customerrequirement• 41% Moved to cloud following industrytrend• 52% Moved to cloud to improve costs,productivity, agility
  3. 3. Why Cloud?
  4. 4. Cloud helps to− Manage Infrastructure Services− Increase Flexibility− Rapid Infrastructure− Cap-ex Free− Rapid Elasticity− Security− Resilience
  5. 5. Pressure points for CIO
  6. 6. CIO pressure points• What do you start with to move to cloud?• How can cloud drive considerable cost and agility benefits for yourorganization?• Does cloud seamlessly integrate with existing workload technologies?
  7. 7. Why migrate?Good riddance to boundaries
  8. 8. Hardware RefreshExpansionHardware exhaustslifecycleReplacementOrder cycleRe-configuration
  9. 9. Why migrate?Because it’s not all ball bearings anymore
  10. 10. Web Applications− Self-contained Web Applications− Social Media Product Marketing Campaigns− Customer Training Sites− Video Portals (Transcoding and Hosting)− Pre-sales Demo Portal− Software Downloads− Trial Applications
  11. 11. Why migrate?Mobilizing healthier business
  12. 12. Green Field applications• Easier to build ground-off applications• Starting off is easier• You can focus more on development ratherthan operational hassles• Development team sees faster results
  13. 13. More reasons to migrate
  14. 14. Test and Develop ApplicationsScalable Test beds withparameters set to test usagepatternsReadymade & PreconfiguredFlexible environments without thehassle of procuring licenses.Option of carrying licenses intothese environments, savingfurther costs.Run Automated Tests3Report ResultsBuild Product142
  15. 15. Here’s what not to migrateImage courtesy: http://www.cloudtweaks.com/cloud-humor/
  16. 16. What NOT to migrate!!!!Legacy, Monolithic, horizontalHome grown CRMsLicense & compatibilityComplexPlan to Migrate firstLow hanging fruitsPlan to Migrate yourcomplex applicationsPlan over 6–12 months
  17. 17. Why migrate?Image courtesy: http://www.cloudtweaks.com/cloud-humor/
  18. 18. Back-Up & Disaster RecoveryExtension to the AWS Cloud forprocessed data or backup dataImprove costs, productivity & ease;improve recovery of dataMove & Back-Up data files,across business functions
  19. 19. SAP Business SuiteSAP HANA OneSAP Business All-in-OneSAP Business Objects- business intelligence solutionsSAP Rapid Deployment Solutions (RDS)SAP AfariaCurrent SAP certified solutions for production on AWS:
  20. 20. And more enterpriseworkload possibilities…
  21. 21. The Challenges
  22. 22. Challenges to migrateIdentifying applications best fit to take advantage of cloudIdentifying right cloud environment - SaaS or PaaS or IaaSIdentifying suitable deployment model - Private /Public /HybridRe-architecting applications for cloudIdentifying & resolving dependence of other application, hardware, firewall,network, security, etc.Planning for business continuity during migration
  23. 23. The 3-D approachEfficiencyCostTime
  24. 24. The 3-D approachEfficiencyCostTime
  25. 25. The 3-D approachEfficiencyCostTime
  26. 26. Cloud Migration Approach
  27. 27. BlazeClans Cloud Migration Approach• Large IT Assets: Enterprises, typically, have a large number of IT Assets• Identify Application: It is important to identify applications for migration• Phase Approach:– Plan– Deploy– Optimize
  28. 28. Phase ApproachPlanDeployExecuteCloud AssessmentProof of conceptDataApplicationLeverage Cloud ArchitectureOptimize Cloud Setup
  29. 29. Cloud Assessment!!!!!!!!Financial AssessmentSecurity & ComplianceAssessmentTechnical & FunctionalAssessmentApplication Mapping interms of dependency treeand Cloud suitabilityIdentifying Cloud vendorMigrating ProductLicensesDefinition of SuccessCriteriaPlan with Roadmap
  30. 30. SaaS, PaaS or IaaS?− Service Level Agreement− Data Portability− Long Term Costs− User management− Security− Scalability Platform Management
  31. 31. Plan Phase – Cloud Assessment− WAN traffic− Data security And Management− Legacy Application Integration− Security and Compliance
  32. 32. Deploy Phase – Data MigrationApplication Data Migration:• Migrate Fileserver systems• Automated scripts for migration• Backups and Tape Drives• Evaluate options to move large sets of data to the Cloud e.g. AWSImport/Export
  33. 33. Deploy Phase – Data MigrationApplication Data Migration:Evaluate options to move large sets of data to the Cloud e.g. AWSImport/ExportBackups and Tape DrivesAutomated scripts for migrationMigrate Fileserver systems
  34. 34. Deploy Phase – Data MigrationDatabase Migration:− Profile the various storage options available in your vendor Cloud− Plan for uploading data in batches− Analyze your datasets and databases− Evaluate various RDBMS options in the Cloud− Ensure data encryption for securitye.g. Amazon RDS
  35. 35. Deploy Phase – Application MigrationForklift MigrationAll components are migrated to cloud atthe same time.Useful for:− Stateless applications− Tightly coupled applications− Self-contained applicationsHybrid MigrationAlso, known as Partial MigrationapproachFor example:− Batch processing in cloud− Application on premise− Integrate cloud applications withcloud incompatible legacyapplications
  36. 36. Optimize Phase – Leverage Cloud Architecture− Auto terminate under-utilized instances through AWS Auto Scale option− Application packaging for AMI construction− Improve data access efficiency
  37. 37. Optimize Phase - Optimize Cloud SetupApplication Re-engineeringAbility to restart on failureSeparation of tiered componentsExtract stateful components and make them statelessDecompose relational database
  38. 38. Migration useCases & scenarios
  39. 39. Web Application MigrationAWS services recommended:EC2, S3, EBS, AS, ELB, CW, RDSMigration of eCommerce website with Mobile extension to createproperty inventory reports of commercial & non-commercial propertieswith an motive of elasticity & scalability
  40. 40. Batch Processing App MigrationAWS services recommended:EC2, EBS, S3, SQS, EMR, DynamoDB, SNSLog analysis and report generations with a motive of faster time toprocess
  41. 41. Backend Process Workflow App MigrationAWS services recommended:EC2, EBS, S3, SQS, EMR, DynamoDB, SNSMigration of Employee Performance Management System with anmotive to lower the total cost of ownership , resilient solution and highavailability
  42. 42. What is moving to Cloud?Trends in Enterprise Application MigrationStorage: 33%ERP: 26%Email: 21%Collaboration: 20%
  43. 43. What is already on the Cloud?Trends in Enterprise Application MigrationStorage: 72%Email: 77%Web Service 74%
  44. 44. BlazeClan Solutions
  45. 45. Plan, report & analyze test results for workloadsTargets:− Online Media & Content Providers− Enterprise Applications− Social Media CampaignsWeb-based Load Testing
  46. 46. Business Case:Enterprise Digital process on Cloud
  47. 47. Business CaseClient• One of India’s largest General & LifeInsurance Company• 4000+ Employees• 200+ LocationsRequirements• Manage Customer Engaging DigitalMarketing campaigns• Ensure accessibility to applicationsall over the internet• Ensure marketing workloads arefast & scalable to adjust to viral• Manage marketing workloads tochange regularly• Enable marketing workloads to rollout quickly
  48. 48. Rapid Deployment:First version of the Application had to be rolled out in 15days2 more releases over the next 15 daysSecurity:Application deals with sensitive dataSeasonal Usage:Application usage peaks between November & MarchMinimal usage for rest of the yearChallenges
  49. 49. Agile DevelopmentSolution delivered in 15 daysAmazon Web ServicesElastic & Scalable infrastructure to save costs during offpeaksPre-build SolutionsPre-configured testing tools to perform vulnerability testingDevelopment using open source tools to save costsSolutionsOpen Source Tools
  50. 50. Low Cost SolutionUsing AWS & Open Source Development tools resultedin significant cost savingsQualityQuick turn aroundAgile Development for fast developmentAdvantagesAutomated TestingEasy to use & secure application
  51. 51. Image references:http://www.gfi.com/blog/why-cloud-based-it-management-makes-sense/, http://www.sharktech.net/index.php?ID=cloud_virtual_servers&PG=2,http://www.patriotsoftware.com/Employer-Training-Blog/bid/57380/5-Reasons-Cloud-Computing-is-Here-to-Stay, http://www.rebeltrail.com/cloud_computing.cfm,http://www.cloudtweaks.com/cloud-humor/, www.soonerworkplace.com, www.marketstar.com, www.dataart.com, www.infotech.uk.com

×