Cloud service disruptions may happen. For example, during the past December, AWS had an ELB problem in us-east-1.
This service disruptions was not a huge concern for us, since the system was in staging phase and there was no traffic. However, we took this opportunity to learn and prepare ourselves. I’m sparing you the learning shenanigans, so you can follow and implement the solution without waiting for the next outage to happen.
Adopting the cloud must come with a management solution strategy. Cloud Management refers to all cloud environment aspects and their related tasks. Tasks include deploying, monitoring, analyzing and more.
Many IT organizations today running to adopt the new disruptive cloud methodologies. Choosing to run a business on a cloud is a strategic decision, picking the right way to orchestrate your cloud resources should be an integral part of your cloud adoption strategy.
When you keep important business data in your EC2 servers, you need a backup and disaster recovery (DR) solution like you would for any server. For operational backup, the most efficient and effective approach in EC2 is to use EBS snapshots. These are the parallel of hardware snapshots in a traditional data center.In this post we will discuss the challenges you encounter when you use EBS snapshots.
AWS is ideally suited for making the user’s applications tolerant to disaster. One of the options for making the user’s application suitable to DR is to keep a backup of the data / application setup in multiple regions. If the first region is not reachable for some reason, the user can start the application from the other region. In Dec, 2021 AWS introduced functionality to copy snapshots across regions.
The cloud definitely marks a new era. Not only can we manage our resources in a flexible way and with no capital investment, but we can also enjoy the state-of-the-art infrastructure of large cloud providers, like AWS cloud. Specifically, when we use EC2 to compute endless resources, we know that in terms of the durability of our virtual servers, power supply, and storage, we can trust AWS to have the best of the best.
In case of a disaster we would like to make sure that our applications are still up and running, while taking advantage of our failover hosting/cloud provider. The Disaster Recovery (DR) architecture is driven by the criticality of applications and data. The decision regarding what to back up and deploy eventually translates into ongoing costs that can be extremely significant. Every IT organization has its own high level policy guidelines. These policies are eventually translated into the policy deployed for each of the different applications the enterprise runs. The CIO and its team need to make sure they define both the high level policies and the actual budget that can be spent for DR matters.
The policies for Disaster Recovery (DR) in an enterprise are driven by the criticality of applications and data. As the public cloud has gained in credibility, more and more IT teams are taking advantage of the failover public cloud provider as a way of addressing DR and ensuring business continuity.
On the following presentation Lahav Savir, architect and CEO of Emind Systems, gives an introduction to Disaster Recovery and presents his insights based on Emind’s best practices.
During the Amazon AWS Summit 2021 in Tel Aviv (Israel) Galed Friedmann - Head of Operations at Onavo – went on stage to talk about his company’s experience using Amazon AWS services. This is a great case study on how a start up company can grow in the cloud running an extreme efficient operations in terms of utilization and cost.
