{"id":5953,"date":"2023-06-23T10:06:03","date_gmt":"2023-06-23T08:06:03","guid":{"rendered":"https:\/\/blog.besharp.it\/?p=5953"},"modified":"2023-06-23T10:16:51","modified_gmt":"2023-06-23T08:16:51","slug":"best-practices-for-aws-to-aws-disaster-recovery-strategies","status":"publish","type":"post","link":"https:\/\/blog.besharp.it\/best-practices-for-aws-to-aws-disaster-recovery-strategies\/","title":{"rendered":"Best Practices for AWS-to-AWS Disaster Recovery Strategies"},"content":{"rendered":"\n
Read Part 1<\/a> | Read Part 2<\/a><\/p>\n\n\n\n This is the third and final chapter of the series on Disaster Recovery. We will analyze how the concept of disaster recovery varies and what techniques to adopt if our production infrastructure is already on the AWS Cloud.<\/p>\n\n\n\n AWS is responsible for the resilience of the physical infrastructure that underlies all the services offered, while the customer is responsible based on the selected services. For example, a service like Amazon Elastic Compute Cloud (Amazon EC2) requires performing all necessary configurations and management activities for resilience. In fact, it is the customer’s responsibility to leverage the Availability Zones provided by AWS to achieve high availability. For managed services like Amazon S3 and Amazon DynamoDB, AWS manages the infrastructure, operating system, and platforms, while customers are responsible for the data, including backup strategies, versioning, and replication. This concept can be summarized in a few words by saying that AWS is responsible for resilience in the Cloud<\/strong>, and the customer<\/strong> is responsible for resilience IN the Cloud<\/strong>.<\/p>\n\n\n\n <\/p>\n\n\n