http://aws.typepad.com/aws/2010/11/new-whitepaper-migrating-your-existing-applications-to-the-aws-cloud.html

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

2. The “Living and Evolving” AWS Cloud Your Application Tools to access services Libraries and SDKs .NET/Java etc. Web Interface Management Console Tools AWS Toolkit for Eclipse Command Line Interface Cross Service features AuthenticationAWS IAM Monitoring Amazon CloudWatch Deployment and Automation AWS Elastic Beanstalk Platform building blocks Content Delivery Amazon CloudFront Email Amazon SES Payments Amazon DevPay Amazon FPS Parallel Processing Amazon Elastic MapReduce Messaging Amazon SNS Amazon SQS Workforce Amazon Mechanical Turk Infrastructure building blocks Compute Amazon EC2 Network Amazon VPC Elastic LB Amazon Route 53 Storage Amazon S3 Amazon EBS Database Amazon RDS Amazon SimpleDB Amazon 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 Assessment Choosing the right candidate Migrating Licensed products Identifying the tools that you can reuse Functional/Architectural assessment

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 Assets Dashboard Report CRM Search DB logs Service LDAP Auth Web Engine OLAP ERP List all your IT assets Identify upward and downward dependencies Start classifying your IT assetsinto different categories: Applications with Top Secret, Secret, or Public data sets Applications with low, medium and high compliance requirements Applications that are internal-only, partner-only or customer-facing Applications with low, medium and high coupling Applications with strict, relaxed licensing

10. How to choose the right candidate for the cloud? Dashboard Report CRM Search DB logs Service LDAP Auth Web Engine OLAP ERP Search for under-utilized IT assets Applications that has immediate business need to scale Applications that are running out of capacity Low-hanging fruits (Examples): Web Applications Batch Processing systems Build/QA/Test systems Content Management Systems Digital Asset Management Systems

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

22. Uploading/Moving your data in Batches

23. Analyzing your database/datasets

24. Build necessary toolsand scripts to migrate data

27. Automate your processes by creating AMIs

29. Process Search Search Billing Billing

31. Implementing “Elasticity”

32. Automating in-cloud software development and deployment lifecycle

33. Increasing high availability by leveraging multiple Availability Zones

35. Hello, I am Mr. Automate Development And Testing Automate Using Cloud APIs Staging and Production Monitoring Build and Deployment

37. Optimizing to increase Performance, improve efficiency and save further costs

38. Implementing Advanced Monitoring and telemetry

39. Ensuring enhanced security

40. Refactoring applications as necessary

42. Cloud Migration: a Phased-driven Strategy

43. http://aws.amazon.com

44. AS AS AS Cloud.com Elastic IP Cloud.com LB LB Auto-scaling group : Web Tier LB ELB: Web Tier EC2.m1.small WS WS Apache Apache Apache Apache Auto-scale: Middle Tier LB HAProxy: Middle Tier EC2.m1.large Tomcat Tomcat Tomcat Tomcat Tomcat DB RDS Master EC2.m1.xlarge Snap shots DBSlave DBSlave RDS(Slave) Amazon S3 EC2.m1.large