Companies have ‘life events’ and we often get the opportunity to work with them at these times as they spur the need for change. In the case of the customer we’re highlighting today, they reached out to the AWS Premier Consulting Partners at Flux7 as they had recently acquired a Canadian-based company for whom they needed to complete a full Disaster Recovery (DR) build out. The firm is subject to Canadian regulations that state that data created in Canada needs to remain stored in Canada. As a result, this audit firm needed a Canadian DR facility that would store all data in country.
Code Spaces. Its story is sending shivers up and down the spines of businesses and developers alike, and for good reason. But that doesn’t mean it should stop the progress of cloud migration or significantly change your strategy. In fact, the story brightly shines a light on an issue that is avoidable, and serves as a warning of what can happen in the complex world of cloud architecture.
This past weekend, we solved two problems for two customers. They both had working configuration management solutions. One used Puppet; the other used Chef. One was Red Hat-based; the other was Debian-based. But, both of them had the same problem.
An organization moving to the cloud truly understand cloud’s benefits only when setting up good DevOps methodologies and cloud automation to meets its needs. The process is replete with tool choices at every stage and the overall goal is to understand and meet the organization’s needs.