Guidance for Backup & Recovery on AWS
How it works
This Guidance demonstrates how to backup your cloud data and resources and perform recovery operations within your cloud environment. It will help you scale when your cloud presence grows, and due to the iterative nature of the capitabilities, you won’t need to start from the beginning. Deploying this Guidance helps ensure you are meeting your business goals, recovery point objectives (RPOs), and recovery time objectives (RTOs), so you have a clear path to host cloud production workloads.
Additional considerations
Another reason is due to the cloud being so highly dynamic, with constant updates, changes, and scaling of resources. This dynamic nature introduces the risk of misconfigurations or system failures, which could lead to the loss of data. Implementing robust backup and recovery procedures means that businesses have a reliable safety net in place, giving them the confidence to experiment, innovate, and adapt to evolving market demands without fearing catastrophic data loss.
Finally, regulatory compliance and data governance are becoming increasingly stringent, with severe penalties for mishandling or failing to protect sensitive information. Properly managed backup and recovery operations in the cloud help organizations maintain compliance with industry regulations and data protection laws. By demonstrating a commitment to data integrity and security through comprehensive backup strategies, businesses can build trust among customers and partners, which is essential for long-term success in today’s competitive and data-driven business landscape.
Related content
- Stakeholders: Central IT (primary), Security, Operations, Finance
- Supporting Capabilities: Governance, Workload Isolation, Identity Management and Access Control, Tagging
- For additional information on this capability, read the whitepaper.
Disclaimer
The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.
References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages