Our Migration to AWS
0 likes170 views
The document outlines Brian McIntyre's migration to Ezora, emphasizing the importance of careful planning and execution in collaboration with AWS. It details the use of automation, version control, and deployment strategies to ensure a successful phased rollout without significant downtime. Key recommendations include selecting a suitable implementation partner, automating processes, and thoroughly planning the migration to optimize benefits such as uptime and geographical redundancy.
Our Migration to AWS
- 4. .
- 5. A Quick Bit Of History...
- 6. .
- 7. .
- 10. Read a lot
- 11. Talk to your AWS Account Manager
- 12. Call with AWS Solutions Architect
- 22. Shell scripts for setting up base AMIs
- 23. User Data scripts to bootstrap new instances
- 24. Fabric & Boto scripts to automate deployment across multiple instances
- 25. Version Control Your Infrastructure
- 26. Start with a simple Git repo
- 27. Put everything in it: AMI setup scripts User Data scripts & launch config details Fabric scripts Backup scripts Crontabs, config files etc...
- 33. Aurora does replicate your data 6 ways across 3 availability zones...
- 34. ...failure of the primary instance can lead to up to 10 mins downtime while it's rebuilt
- 37. Going Live
- 39. Phased rather than a big-bang approach
- 40. Staged rollout, by client, over 3 weeks
- 42. Main Benefits
- 43. Peace of mind
- 44. Uptime
- 45. Geographical redundancy, automated scaling, flexibility
- 46. Access to new features/services
- 47. Ability to stand over our infrastructure
- 48. Some Issues
- 49. Beanstalk
- 51. EC2 swap space
- 52. Backup - RDS policies & pricing
- 53. Aurora patching & failover
- 55. Choose your implementation partner carefully
- 56. Version & automate everything
- 57. Make the most of AWS & IaaS
- 58. Plan your migration process in detail
- 59. Closing Thoughts
- 60. Cost
- 61. Effort
- 62. Reward