The document discusses a phased approach to migrating applications to the cloud, emphasizing assessments such as financial, security, and technical evaluations. It highlights the importance of choosing suitable candidates for migration, addressing data ownership and sensitivity, and implementing security practices. Additionally, it covers leveraging AWS services for automation, optimization, and effective resource management in the cloud environment.

1. Migrating Existing Applications To The Cloud: A Phased Driven approach to Cloud MigrationJinesh Varia

2. The “Living and Evolving” AWS CloudYour ApplicationTools to access servicesLibraries and SDKs.NET/Java etc.Web InterfaceManagement ConsoleToolsAWS Toolkit for EclipseCommand Line InterfaceCross Service featuresAuthenticationAWS IAMMonitoringAmazon CloudWatchDeployment and AutomationAWS Elastic BeanstalkPlatform building blocksContent DeliveryAmazon CloudFrontEmailAmazon SESPaymentsAmazon DevPayAmazon FPSParallel ProcessingAmazon Elastic MapReduceMessagingAmazon SNSAmazon SQSWorkforceAmazon Mechanical TurkInfrastructure building blocksComputeAmazon EC2 NetworkAmazon VPCElastic LBAmazon Route 53StorageAmazon S3Amazon EBSDatabaseAmazon RDSAmazon SimpleDBAmazon Global Physical Infrastructure (Geographical Regions, Availability Zones, Edge Locations)

3. A Phased Driven approach to Cloud Migration

5. Includes:Financial Assessment (TCO/ROI Analysis)Security and Compliance Assessment Technical AssessmentChoosing the right candidateMigrating Licensed productsIdentifying the tools that you can reuseFunctional/Architectural assessment

6. Security and Compliance AssessmentYou own the data, not AWS.

7. You choose which geographic location to store the data. It doesn’t move unless you decide to move it.

8. You should consider the sensitivity of your data and decide if and how you will encrypt your data while it is in transit and while it is at rest.Involve your Security Teams early in the process

9. Create a Dependency Tree of your IT AssetsDashboardReportCRMSearchDBlogsServiceLDAPAuthWebEngineOLAPERPList all your IT assetsIdentify upward and downward dependenciesStart classifying your IT assetsinto different categories:Applications with Top Secret, Secret, or Public data setsApplications with low, medium and high compliance requirementsApplications that are internal-only, partner-only or customer-facingApplications with low, medium and high couplingApplications with strict, relaxed licensing

10. How to choose the right candidate for the cloud?DashboardReportCRMSearchDBlogsServiceLDAPAuthWebEngineOLAPERPSearch for under-utilized IT assetsApplications that has immediate business need to scaleApplications that are running out of capacityLow-hanging fruits (Examples):Web ApplicationsBatch Processing systemsBuild/QA/Test systemsContent Management SystemsDigital Asset Management Systems

11. Includes:Get your feet wet with Amazon Web Services

12. Learning AWS

13. Build reference architecture

14. Be aware of the security features

15. Build a Prototype/Pilot

16. Build support in your organization

17. Validate the technology

18. Test legacy software in the cloud

19. Perform benchmarks and set expectationsGet your feet wet – In the cloud in 5 minutes

21. Includes:Learning about different database storage options available today

22. Uploading/Moving your data in Batches

23. Analyzing your database/datasets

24. Build necessary toolsand scripts to migrate data