Skip to content

Lesson 05 — Enterprise Backup, Disaster Recovery & Business Continuity Project & Module Review

Learning Path

☁️ Phase 02 – AWS Cloud Security

📘 Module 10 – Backup, Disaster Recovery & Business Continuity


By the end of this lesson, you will be able to:

  • Design an enterprise Backup strategy.
  • Build Disaster Recovery architectures.
  • Perform Disaster Recovery planning.
  • Develop Business Continuity Plans.
  • Recover enterprise workloads.
  • Validate recovery objectives.
  • Present security recommendations to executive leadership.

📚 Lesson Information

Estimated Time: 6 Hours

Difficulty: Advanced

Prerequisites: Lessons 01–04

Hands-on Project: Yes


CloudNova Technologies has become a global Software-as-a-Service (SaaS) provider operating across multiple AWS Regions.

The environment now contains:

  • 80 AWS Accounts
  • 5 AWS Regions
  • 2,500 Amazon EC2 Instances
  • 750 Amazon RDS Databases
  • Amazon Aurora Clusters
  • Amazon EKS Clusters
  • Amazon EFS
  • Amazon FSx
  • Amazon S3 Data Lakes
  • Financial Applications
  • Customer Portals
  • AI Platforms

CloudNova is preparing for:

  • ISO 27001 Certification
  • SOC 2 Audit
  • PCI DSS Assessment

Before the audit begins, disaster strikes.

A sophisticated ransomware attack encrypts production workloads while an unexpected network failure causes the primary AWS Region to become unavailable.

Immediate impacts include:

  • Customer Portal Offline
  • Payment Services Unavailable
  • Database Replication Interrupted
  • Internal ERP Unavailable
  • Customer Support Delayed
  • Executive Dashboard Offline

The Board of Directors asks:

“Can we recover quickly without losing critical business data while continuing to serve our customers?”

As the Cloud Security Engineer, you are responsible for leading the technical recovery effort and demonstrating that CloudNova has a mature Backup, Disaster Recovery and Business Continuity programme.


During this capstone project you will implement an enterprise solution using:

  • AWS Backup
  • Backup Vaults
  • Backup Plans
  • AWS KMS
  • Cross-Account Backup
  • Cross-Region Backup
  • Disaster Recovery Strategies
  • Route 53 Failover
  • Business Continuity Planning
  • Recovery Runbooks
  • Executive Reporting

AWS Organizations
┌──────────────────────┼──────────────────────┐
│ │ │
Production Account DR Account Backup Account
│ │ │
AWS Backup Warm Standby Backup Vault
│ │ │
Amazon EC2 Amazon EC2 AWS KMS
Amazon RDS Amazon RDS Lifecycle Policies
Amazon EFS Amazon EKS Cross-Region Copies
Amazon EKS Route 53
Recovery Testing
Business Continuity
Executive Dashboard

CloudNova requires the following outcomes.

✔ Enterprise Backup Strategy

✔ Secure Backup Storage

✔ Cross-Region Recovery

✔ Cross-Account Protection

✔ Disaster Recovery Plan

✔ Business Continuity Plan

✔ Recovery Runbooks

✔ Executive Reporting


Review the existing AWS environment.

Identify:

  • Critical Workloads
  • Current Backup Strategy
  • Backup Frequency
  • Backup Retention
  • Encryption Status
  • Backup Gaps

Deliverable:

Enterprise Backup Assessment Report.


Phase 02 — Design Enterprise Backup Strategy

Section titled “Phase 02 — Design Enterprise Backup Strategy”

Create backup policies for:

  • Amazon EC2
  • Amazon EBS
  • Amazon RDS
  • Amazon Aurora
  • Amazon DynamoDB
  • Amazon EFS
  • Amazon FSx
  • Amazon S3

Include:

  • Daily Backups
  • Weekly Backups
  • Monthly Backups
  • Long-Term Retention
  • Backup Vault Encryption

Deliverable:

Enterprise Backup Design.


Configure:

  • Backup Vaults
  • AWS KMS Keys
  • Backup Vault Access Policies
  • Lifecycle Policies
  • Resource Tags
  • Backup Monitoring

Implement:

  • Cross-Account Backup
  • Cross-Region Backup

Deliverable:

Secure Backup Architecture.


Select Disaster Recovery strategies for each workload.

Workload Recommended Strategy
Payment Platform Multi-Site Active/Active
Customer Portal Warm Standby
ERP System Pilot Light
HR Application Backup & Restore
Development Backup & Restore

Document:

  • RPO
  • RTO
  • Recovery Order
  • Failover Process

Deliverable:

Disaster Recovery Plan.


Perform a Business Impact Analysis.

Identify:

  • Critical Business Processes
  • Business Owners
  • Financial Impact
  • Operational Impact
  • Regulatory Impact

Develop:

  • Business Continuity Plan
  • Crisis Communication Plan
  • Recovery Priorities
  • Executive Escalation Matrix

Deliverable:

Business Continuity Documentation.


At 09:15 AM:

  • Primary AWS Region fails.
  • Production database becomes unavailable.
  • Customer Portal is offline.
  • Payment processing stops.
  • Employees cannot authenticate.

The executive team declares a Disaster Recovery event.

Your responsibilities include:

  • Assessing the incident.
  • Initiating failover.
  • Restoring workloads.
  • Validating application functionality.
  • Communicating progress to stakeholders.
  • Coordinating business recovery.

Incident Detected
SOC Notification
Executive Approval
Disaster Declared
Failover Initiated
Infrastructure Recovery
Database Recovery
Application Validation
Customer Services Restored
Executive Sign-Off
Lessons Learned

Verify the following.

Control Status
Backup Vault Available
Recovery Point Verified
EC2 Restored
RDS Restored
Route 53 Failover Completed
Application Available
Customer Authentication Working
Security Controls Operational
Monitoring Enabled
Business Services Operational

During the exercise, CloudNova identifies the following issues.

Production EC2 Instances encrypted by ransomware.

Expected Action

  • Restore from AWS Backup.
  • Validate operating system integrity.
  • Patch affected systems.
  • Perform malware investigation.

Primary Region unavailable.

Expected Action

  • Initiate Route 53 failover.
  • Activate Disaster Recovery Region.
  • Validate DNS propagation.

Production Database unavailable.

Expected Action

  • Restore database.
  • Validate application connectivity.
  • Confirm data consistency.

Backup Job Failure

Expected Action

  • Investigate IAM permissions.
  • Review Backup Vault.
  • Restart failed jobs.

Customer Support Platform unavailable.

Expected Action

  • Activate Business Continuity procedures.
  • Redirect support teams.
  • Notify customers.

Prepare the following documents.


Include:

  • Backup Coverage
  • Backup Success Rate
  • Recovery Points
  • Encryption Status
  • Retention Policy

Include:

  • Recovery Strategy
  • Failover Timeline
  • Actual RPO
  • Actual RTO
  • Recovery Success

Summarise:

  • Business Impact
  • Critical Services
  • Communication Timeline
  • Recovery Priorities
  • Operational Status

Present:

  • Backup Success Rate
  • Recovery Readiness
  • Recovery Testing Results
  • Business Availability
  • Disaster Recovery Status
  • Compliance Status
  • Risk Level

Include:

  • Successes
  • Recovery Challenges
  • Technical Improvements
  • Process Improvements
  • Future Recommendations

Create:

  • Backup Vault
  • Backup Plan
  • Backup Rules

Validate successful backups.


Configure:

  • Cross-Region Backup
  • Cross-Account Backup

Verify recovery points.


Restore:

  • Amazon EC2
  • Amazon RDS
  • Amazon EBS

Validate application functionality.


Simulate a Regional Failure.

Perform:

  • Route 53 Failover
  • Application Recovery
  • Database Recovery

Record actual recovery times.


Conduct a Business Impact Analysis.

Document:

  • Critical Services
  • Recovery Priorities
  • Business Owners
  • Recovery Objectives

Prepare an Executive Recovery Presentation covering:

  • Business Impact
  • Recovery Timeline
  • Technical Recovery
  • Business Recovery
  • Lessons Learned
  • Future Improvements

Terminal window
aws backup list-backup-vaults

Terminal window
aws backup list-backup-plans

Terminal window
aws backup list-backup-jobs

Terminal window
aws backup list-recovery-points-by-backup-vault \
--backup-vault-name ProductionVault

Terminal window
aws backup list-restore-jobs

Terminal window
aws route53 list-health-checks

Terminal window
aws cloudwatch describe-alarms

CloudNova standards include:

  • Define Recovery Point Objective (RPO) and Recovery Time Objective (RTO) for every critical application.
  • Encrypt every Backup Vault using customer-managed AWS KMS keys.
  • Enable Cross-Account and Cross-Region backups.
  • Test Disaster Recovery at least quarterly.
  • Review Business Continuity Plans annually.
  • Automate infrastructure deployment using Infrastructure as Code (IaC).
  • Validate every restore before returning systems to production.
  • Maintain documented recovery runbooks and communication plans.
  • Continuously monitor backup success, recovery readiness and business resilience.

❌ Treating backups as Disaster Recovery.

❌ Never performing recovery testing.

❌ Storing all backups in a single AWS account.

❌ Ignoring application dependencies.

❌ Failing to define business recovery priorities.

❌ Forgetting executive communication during disasters.

❌ Not updating Business Continuity documentation after organisational changes.


CloudNova plans to expand globally and must guarantee resilient services for millions of customers.

Design a complete enterprise Backup, Disaster Recovery and Business Continuity programme that includes:

  1. Enterprise Backup Strategy.
  2. AWS Backup Architecture.
  3. Cross-Account and Cross-Region protection.
  4. Disaster Recovery Architecture.
  5. Business Impact Analysis.
  6. Crisis Communication Plan.
  7. Recovery Runbooks.
  8. Disaster Recovery Testing Programme.
  9. Executive Dashboard.
  10. Continuous Improvement Programme.

Prepare the following documents:

  • Enterprise Backup Strategy
  • Disaster Recovery Architecture
  • Business Continuity Plan
  • Business Impact Analysis
  • Executive Dashboard
  • Disaster Recovery Runbook
  • Crisis Communication Plan
  • Lessons Learned Report
  • Executive Recovery Report

Congratulations!

You have successfully completed Module 10 – Backup, Disaster Recovery & Business Continuity.

You can now:

✅ Design enterprise backup strategies

✅ Protect workloads using AWS Backup

✅ Secure backups with encryption

✅ Implement Cross-Account and Cross-Region recovery

✅ Build Disaster Recovery architectures

✅ Calculate and apply RPO and RTO

✅ Perform Disaster Recovery testing

✅ Develop Business Continuity Plans

✅ Coordinate crisis communication

✅ Present recovery metrics to executive leadership


  1. What is the difference between Backup, Disaster Recovery and Business Continuity?
  2. Why are RPO and RTO critical when designing recovery solutions?
  3. What are the benefits of Cross-Account and Cross-Region backups?
  4. When would you choose a Warm Standby architecture instead of Backup & Restore?
  5. Why should recovery procedures be tested regularly?
  6. What is the purpose of a Business Impact Analysis?
  7. What information should be included in a Disaster Recovery Runbook?
  8. Why is crisis communication important during major incidents?
  9. Which AWS services help automate backup and recovery?
  10. How do Backup, Disaster Recovery and Business Continuity work together to improve organisational resilience?

After completing this module, you should understand:

  • Enterprise resilience depends on the integration of Backup, Disaster Recovery and Business Continuity rather than any single capability.
  • AWS Backup provides centralised protection for AWS workloads through Backup Plans, Backup Vaults, Lifecycle Policies and secure recovery operations.
  • Disaster Recovery architectures should be selected based on business-driven RPO and RTO requirements, balancing cost with availability.
  • Business Continuity ensures critical operations continue through effective planning, communication, recovery priorities and regular testing.
  • Cloud Security Engineers play a key role in protecting business operations by designing resilient architectures, validating recovery procedures and continuously improving organisational readiness.

Excellent work!

You have successfully completed Module 10 – Backup, Disaster Recovery & Business Continuity.

You now have the practical knowledge to:

  • Build enterprise backup solutions.
  • Design disaster recovery architectures.
  • Lead technical recovery during major incidents.
  • Develop business continuity programmes.
  • Validate organisational resilience.
  • Support audit and regulatory requirements.
  • Protect critical business services using AWS best practices.

➡️ Module 11 — DevSecOps & Infrastructure as Code (IaC) Security

In the next module, you will learn how to:

  • Secure CI/CD pipelines.
  • Build Infrastructure as Code (IaC) using AWS CloudFormation and Terraform.
  • Detect secrets and vulnerabilities in source code.
  • Secure container build pipelines.
  • Integrate automated security testing into DevOps workflows.
  • Apply policy-as-code and compliance-as-code.
  • Build secure software delivery pipelines following enterprise DevSecOps best practices.

This module transitions from operational resilience to building secure cloud infrastructure and applications from the very beginning of the software development lifecycle (SDLC).