Ezhil Arasan Babaraj, Director CSS Corp Labs, Presenting at SiliconIndia Cloud Developer Summit. "Track B: Cloud Infrastructure" at Session 7 Date & Time: 14th May 2011 & 2.45 PM to 3.30 PM Topic: "Bullet Proof Your AWS Cloud Deployment" Location: Nimhans Convention Centre, Bangalore - 560029

1. Bullet proof your Amazon Cloud Deployment EzhilArasanBabaraj Director – CSS Corp Labs CSS Corp Twitter : @ezhilsathya Blog : http://cloud4developers.com/

3. Driving Technology Innovation and adoption

4. Technology OpEx Optimization

5. Transparency ,Openness & Flexibility

7. Dedicated CSS Labs for Technology Innovation

8. Business Operations and Technology Optimizer

9. Out-comes based pricing models

10. Top Mid Market ITO Provider 2007,2008,2009 – DataMonitor

11. Recognized leader in Technology Operations Management with CoEs in Telecom, SaaS, Cloud, RIM, Testing, Support and R&D

12. Strong Partner Ecosystem; AWS, Microsoft, IBM, HP

13. 150+ Long Term, Strategic and Profitable Customers

14. Operations in USA, UK, Poland, India, Manila & Singapore

16. 5,000+ Resources

17. Market Validation – 100% Client Retention

20. Technical Assessment

21. Financial Assessment

22. CLIENT Cloud Deployment Architecture

23. Private Cloud Deployment Architecture

24. OSS Strategy (COTS Vs In-house Tools)

25. Build a pilot to validate technology

26. AMI Creation

27. Forklift / Hybrid Migration of applications

28. Tools Deployment

29. Runbook Development

31. Cascading Failures

32. Designing for Failure

33. Testing for Failure

35. Application Deployment

36. Database Deployment

37. Data Backup and Recovery

38. Automation of Deployment

39. Disaster Recovery

41. Applications Fail

42. Databases Fail

43. Infrastructure Fails

44. Cloud Fails

46. Appropriate use of Cloud Tools

47. Draft a Good backup strategy

48. Implement Monitoring & Alerting

49. Ensure Effective Recovery Mechanisms

51. Multiple Regions

52. Availability Zones

53. Machine Images(AMI)

54. EBS Volumes

55. Security Groups

57. Multiple Regions

58. Availability Zones

59. Machine Images(AMI)

60. EBS Volumes

61. Security Groups

63. Ability to take Snapshots

64. Ability to stop instances

65. Variable Root Disk Sizes

67. Launch AMI

68. Customize Instance

69. Install Provisioning Agent

70. Bundle the Instance=New AMI

72. Easy to maintain deployment

73. Dynamic Configurations

74. Development knowledge

76. Best when publicizing

77. An AMI for Every Version

78. Cumbersome to Maintain

80. Network File Sharing & Virtual SAN

81. Offsite / Remote Backups

82. Distributed / Replicated FS

83. Remote Server Sync

85. Would do with some data loss

86. Better cost benefit

88. Higher cost of running

89. All updates and patch need to be applied

91. Keep 2 level redundant backups

92. Define maintenance windows

94. Run all the components

95. Back up all data frequently

98. Database Backup

99. Bring down the Live Environment

100. AMI with CloudSmart on DR Region

101. Script CloudSmart for DR

103. We managed to survive © 2010 CSS Corporation 20 The AWS US East Outage

105. Queue for storing messages – Simple Queue Service

106. Email sending service – Simple Email Service

107. Publish message / Subscription to messages - Simple Notification Service

108. Non-relational Data Store – Simple DB

109. Relational Database MySQL / Oracle – Relational Database Service