# AWS Backup

> Source: Courseiva IT Certification Glossary — https://courseiva.com/glossary/aws-backup

## Quick definition

AWS Backup is a tool that helps you automatically save copies of your data from various AWS services like virtual servers, databases, and file storage. Instead of setting up backups manually for each service, you create a single plan that runs on a schedule. It stores your backups safely and lets you restore them if something goes wrong, like accidental deletion or a system failure. Think of it as a central command center for all your data protection needs in the cloud.

## Simple meaning

Imagine you have several different devices at home: a laptop, a tablet, a smartphone, and a game console. Each one has important data like photos, documents, and game saves. If you wanted to back everything up, you might have to plug each device into a separate backup drive and remember to do it every week. That is a lot of work and easy to forget.

AWS Backup works like a smart, automated assistant that takes care of all your different cloud services in one place. You tell it once what you want to back up, how often, and how long to keep the backups. Then it does the work for you, checking in on your virtual servers (EC2 instances), databases (RDS, DynamoDB), file systems (EFS), and storage volumes (EBS). It creates copies of your data without you needing to log into each service separately.

These copies are stored in a secure vault. If you accidentally delete something, or if a system crashes, you can go to the AWS Backup dashboard, find the backup you need, and restore your data with a few clicks. It is like having a safety net that catches you when things go wrong. AWS Backup also keeps track of all backup activities, so you can see when backups ran, if any failed, and whether your data is safe according to your company’s rules. This makes it much easier for IT teams to meet compliance requirements and protect against data loss, all without writing complex scripts or managing backup software.

## Technical definition

AWS Backup is a cloud-native, policy-based backup service that integrates deeply with over a dozen AWS services. It provides centralized backup management across compute, storage, and database resources. The service uses backup plans, which are JSON or console-defined policies that specify a frequency (e.g., daily at 2 AM UTC), a retention period (e.g., 35 days), and a lifecycle rule (e.g., move to cold storage after 30 days). Each backup is stored as a recovery point within a backup vault, which can optionally be locked (using AWS Backup Vault Lock) to enforce a Write Once Read Many (WORM) state for compliance.

Under the hood, when a backup plan triggers, AWS Backup communicates with the source service via its API to create a snapshot or a backup. For Amazon EBS volumes, it creates point-in-time snapshots stored in Amazon S3. For Amazon RDS, it triggers automated DB snapshots. For DynamoDB, it uses on-demand backups. For Amazon EFS and FSx, it uses AWS Backup’s own incremental backup engine, which captures only changed blocks, reducing storage costs and time. For EC2 instances, AWS Backup can orchestrate a snapshot of all attached EBS volumes and store instance metadata, enabling full instance recovery.

Backup plans can be assigned to AWS resources using tags, ARNs, or resource IDs. This tag-based assignment is crucial for automation and scaling: as new resources are created with the correct tag, AWS Backup automatically applies the policy. The service also supports cross-account and cross-region backup copies. A backup can be copied to another AWS region for disaster recovery and to another account for isolation. All backup activities are logged in AWS CloudTrail for auditing, and metrics like backup success/failure and size are sent to Amazon CloudWatch. AWS Backup is built on a pay-as-you-go model: you pay for the storage consumed by recovery points and for any data transferred for cross-region copies. Restoring from a backup may require launching new resources, and the restore time depends on the source service (e.g., restoring a multi-TB RDS instance takes longer than a small EBS volume). The service is designed for enterprises that need a single, auditable, and policy-driven approach to data protection, reducing the operational overhead of managing backups per service.

## Real-life example

Think of AWS Backup like having a professional document management service for a busy office. You have many employees working on different projects, each storing files in various cabinets, digital drives, and databases. Without a central system, each employee would be responsible for making copies of their own work, which leads to inconsistency, missed deadlines, and lost files when someone forgets.

With the document management service, you hire a manager (AWS Backup) who visits every cabinet and drive once a day, takes a photocopy of everything that changed, and stores those copies in a secured, fireproof vault. The manager follows a master plan: every night at midnight, copy all new documents. Keep daily copies for one month. Keep monthly copies for one year. If an employee accidentally deletes a critical file, the manager goes to the vault, finds the correct version, and puts it back in the right place. This saves the employee hours of rework.

In the IT world, your “employees” are cloud services like EC2 instances, RDS databases, and EFS file systems. The “manager” is AWS Backup, which automatically takes snapshots or backups according to a central policy. The “vault” is a secure storage service. If a developer accidentally runs a dangerous script that corrupts a database, the IT team restores from the most recent backup created by AWS Backup. The entire process is automated, auditable, and consistent. This analogy shows why AWS Backup is so valuable: it reduces the risk of human error, ensures compliance, and gives you peace of mind knowing that your data is protected by a systematic, repeatable process rather than relying on individual actions.

## Why it matters

In any IT environment, data loss is a major risk that can lead to financial loss, reputational damage, and even legal penalties. AWS Backup matters because it provides a standardized, automated way to protect data across a diverse set of AWS services. Without it, IT teams often need to learn the backup interface of each service separately, create manual scripts using AWS CLI or SDK, and set up monitoring for each service. This is time-consuming, error-prone, and hard to audit.

AWS Backup simplifies compliance. Many industries require companies to keep backups for a certain period and store them in an immutable format. AWS Backup Vault Lock provides exactly that: once locked, no one can delete or modify backups until the retention period ends. This helps organizations pass audits and meet regulations like HIPAA, GDPR, and SOC 2. The service also provides a centralized dashboard where you can see all backup jobs, their status, and storage costs, making it easier to report on data protection status.

For disaster recovery, AWS Backup allows you to copy backups to another AWS region. If your primary region goes down, you can restore your data in a different region and resume operations. This is critical for business continuity. Because AWS Backup integrates with AWS Organizations, you can deploy backup policies across hundreds of AWS accounts from a single management account, ensuring consistent protection across the entire organization. AWS Backup reduces complexity, enforces standards, and gives IT professionals a reliable tool to safeguard data, which is a core responsibility of any infrastructure or operations role.

## Why it matters in exams

AWS Backup is a topic that appears in several AWS certification exams, particularly the AWS Certified Solutions Architect Associate (SAA-C03), AWS Certified SysOps Administrator Associate (SOA-C02), and the AWS Certified Data Analytics Specialty (DAS-C01). It is also relevant for the AWS Certified Security Specialty (SCS-C02) when discussing data protection and compliance. Exam questions typically test your understanding of how to design backup strategies, choose appropriate retention policies, and configure cross-region or cross-account backups.

In the Solutions Architect exam, you might see a scenario where a company has EC2 instances with EBS volumes, an RDS database, and an EFS file system. The question asks for a single solution to back up all of these resources with a 30-day retention policy. The correct answer is AWS Backup because it supports all three services natively. A distractor might be creating separate Lambda functions or using native snapshot APIs, but those are more complex and not managed centrally. The exam also tests your knowledge of AWS Backup Vault Lock for compliance: if a question states that backups must not be deletable by anyone, you must enable Vault Lock.

For the SysOps exam, you are expected to know how to create backup plans, assign resources using tags, and monitor backup jobs in the console or via CloudWatch. You might be asked to troubleshoot a failed backup: for instance, if a backup plan is not backing up a new EC2 instance, the likely cause is that the instance is not tagged with the required tag key-value pair. Another common question involves cost optimization: what happens if you back up an EBS volume daily but only need weekly recovery points? You would configure a lifecycle policy to transition older backups to cold storage or expire them.

The exams also emphasize the concept of incremental backups for EFS and FSx. A question might describe a large file system with frequent changes and ask which AWS service provides cost-effective, incremental backups. AWS Backup is the answer. Understanding that AWS Backup uses incremental backups for certain services (not for EBS snapshots, which are differential) is a key exam point. Overall, AWS Backup appears in at least two to three questions per exam, focusing on automation, centralization, and compliance features.

## How it appears in exam questions

AWS Backup questions in certification exams typically fall into three categories: scenario-based design, configuration, and troubleshooting. In a scenario-based question, you are given a business requirement and asked to select the best backup strategy. For example: “A company has 50 EC2 instances running a web application, each with a 100 GB EBS volume. They also have an RDS MySQL database and an EFS file system for shared storage. They want a single, automated backup solution with 7-day retention and the ability to restore any instance or database quickly. Which service should they use?” The correct answer is AWS Backup, because it supports EC2 (via EBS snapshots), RDS, and EFS in a unified backup plan. Distractors might include using individual service snapshots with a custom scheduler, which is less efficient.

Configuration questions ask you to interpret a backup plan definition. For instance: “A backup plan specifies a daily backup at 12:00 AM UTC, retention of 30 days, and a lifecycle rule that transitions backups to cold storage after 7 days. What is the total time a recovery point will remain available in standard storage?” The answer is 7 days, because the lifecycle rule moves it to cold storage after 7 days, though it is still accessible (but at lower cost and possibly longer restore time). Another common configuration question involves tags: “How can you ensure that any new EC2 instance launched with the tag ‘Environment: Production’ is automatically backed up?” The answer is to assign the backup plan to resources with that specific tag.

Troubleshooting questions often revolve around why a backup did not run. For example: “An administrator created a backup plan and assigned it to resources by tag. Some resources are being backed up, but one EC2 instance is not. What is the most likely cause?” The answer is that the EC2 instance does not have the correct tag, or the tag value is wrong. Another troubleshooting scenario: “A backup job failed with the error ‘Insufficient permissions.’” The likely cause is that the AWS Backup service role does not have the necessary permissions to take snapshots of the target resource. The fix is to attach the AWS managed policy AWSBackupServiceRolePolicyForBackup to the IAM role used by AWS Backup. These question types test your practical understanding of how AWS Backup interacts with IAM, tagging, and resource configuration.

## Example scenario

Scenario: TechRetail Inc. runs its e-commerce platform on AWS. They have three EC2 instances (web servers) with attached EBS volumes, one RDS PostgreSQL database for orders, and two EFS file systems for product images. The IT manager wants to automate backups so that all data is protected nightly, backups are kept for 14 days, and they can restore any resource quickly. The manager also wants to ensure backups are stored in a different AWS region for disaster recovery.

Solution with AWS Backup: The IT team creates a single backup plan called “DailyNightly” with a rule that triggers at 2:00 AM UTC every day. The retention period is set to 14 days. They also configure a copy action to copy each backup to the us-west-2 region (their DR region), retaining those copies for 14 days as well. They then tag all EC2 instances, the RDS database, and both EFS file systems with the tag key “Backup” and value “Daily.” Finally, they assign the backup plan to all resources with that tag.

Result: Every night, AWS Backup automatically takes snapshots of EBS volumes (attached to EC2), triggers an RDS snapshot, and performs incremental backups of the EFS file systems. All recovery points are stored in a vault in the primary region (us-east-1) and then copied to us-west-2. After 14 days, older recovery points are automatically deleted. If a developer accidentally deletes a product image from the EFS file system, the team can restore the file from the most recent backup in a few minutes. If the entire primary region fails, they can restore the RDS database and EFS from the copies in us-west-2, launching new EC2 instances there. This scenario demonstrates how AWS Backup simplifies data protection and disaster recovery across multiple AWS services.

## Common mistakes

- **Mistake:** Confusing AWS Backup with native snapshots of individual services like EBS Snapshots or RDS automated backups.
  - Why it is wrong: AWS Backup is a centralized orchestration layer that uses the native snapshot capabilities of each service, but it adds policy management, automation, cross-region copy, and a single dashboard. Using only native snapshots means you have to manage each service separately, which is less efficient and not scalable.
  - Fix: Think of AWS Backup as a manager that schedules and coordinates backups across services, while native snapshots are the individual tools. Use AWS Backup when you need a unified, policy-driven solution.
- **Mistake:** Assuming that AWS Backup automatically backs up all AWS resources in an account without any configuration.
  - Why it is wrong: AWS Backup does not back up anything until you create a backup plan and assign it to specific resources or resource tags. It is not an automatic blanket protection service. You must define policies and assign them.
  - Fix: Always explicitly create a backup plan and assign it to resources, either individually or using tags. Verify that resources have the correct tags before expecting backups to run.
- **Mistake:** Thinking that AWS Backup can back up resources that are not supported by the service.
  - Why it is wrong: AWS Backup supports only specific AWS services, such as EC2, RDS, DynamoDB, EFS, FSx, Storage Gateway, and a few others. It cannot back up custom applications running on EC2 at the application level unless via third-party integrations.
  - Fix: Check the official AWS Backup documentation for the current list of supported services. For unsupported resources, you may need to use other tools like AWS Systems Manager or custom scripts.
- **Mistake:** Forgetting that cross-region backup copies incur data transfer costs and may have longer restore times.
  - Why it is wrong: Some learners assume cross-region copies are free or instantaneous. In reality, data transfer between regions is billed, and restoring from a cross-region copy takes longer because data must be transferred over the network.
  - Fix: Always account for data transfer costs in your design. Use cross-region copies only for disaster recovery or compliance, not for routine restores. Test restore times to ensure they meet your recovery time objective (RTO).
- **Mistake:** Assuming that enabling AWS Backup Vault Lock is optional and can be applied after a backup is created.
  - Why it is wrong: Vault Lock must be configured when creating or modifying a vault, and once you set the lock (in compliance mode), it cannot be reversed. If you try to lock a vault after backups exist, you may need to create a new vault. Also, if you do not lock it, backups can be deleted accidentally.
  - Fix: Plan vault lock configurations upfront for compliance. Use governance mode for flexibility, or compliance mode for irrevocable protection. Test lock settings on a non-production vault first.

## Exam trap

{"trap":"The exam might present a scenario where a company wants to back up an on-premises file server to AWS, and the distractors include AWS Backup as a native solution.","why_learners_choose_it":"Because AWS Backup is described as a centralized backup service, learners might mistakenly think it can directly connect to on-premises infrastructure. AWS Backup is primarily designed for AWS-native resources.","how_to_avoid_it":"Remember that AWS Backup works with AWS services. For on-premises file servers, you need to use AWS Storage Gateway (specifically the File Gateway or Volume Gateway) to present storage to AWS, and then AWS Backup can back up the gateway’s data. Alternatively, use AWS DataSync or third-party backup software. Always check if the resource is inside AWS."}

## Commonly confused with

- **AWS Backup vs AWS DataSync:** AWS DataSync is used for transferring large amounts of data to and from AWS, often for migration or sync purposes, not for scheduled, policy-based backups. DataSync can move data from on-premises to AWS, but it does not manage retention policies, vaults, or point-in-time recovery like AWS Backup. AWS Backup focuses on snapshot-based protection of AWS resources. (Example: Use DataSync to copy 10 TB of files from an on-premises NAS to Amazon EFS, then use AWS Backup to automatically back up that EFS file system nightly.)
- **AWS Backup vs Amazon S3 Versioning:** S3 Versioning protects objects within an S3 bucket by keeping multiple versions of an object. AWS Backup does not directly back up S3 objects; instead, it can back up S3 buckets using the S3 backup integration, but versioning is a native S3 feature. AWS Backup provides a centralized backup policy across multiple services, while S3 Versioning is specific to one bucket. (Example: Enable S3 Versioning on a bucket to recover from accidental overwrites. Use AWS Backup to create a cross-region copy of the same bucket for disaster recovery.)
- **AWS Backup vs Amazon RDS Automated Backups:** RDS automated backups are a native feature of RDS that creates daily snapshots and transaction logs. AWS Backup can also create RDS snapshots, but it provides a unified policy across services, cross-region copy, and audit logging. RDS automated backups are simpler but not centrally managed. (Example: For a single RDS database, RDS automated backups work fine. For an environment with EC2, EFS, and RDS, use AWS Backup to manage all backups with one schedule.)

## Step-by-step breakdown

1. **Create a Backup Vault** — First, you create a backup vault which is a logical container for storing recovery points. You can optionally enable Vault Lock to enforce a retention policy and prevent deletion. This step matters because it organizes your backups and provides security controls. You can create multiple vaults for different environments (e.g., Production, Development) to separate backups.
2. **Define a Backup Plan** — A backup plan specifies the schedule (e.g., daily at 1 AM), the retention window (e.g., keep for 7 days), and lifecycle rules (e.g., move to cold storage after 3 days). You can also add a copy rule to send backups to another region or account. This step is critical because it automates the backup frequency and ensures compliance with company policies.
3. **Assign Resources to the Backup Plan** — You assign the backup plan to AWS resources using either resource IDs (e.g., specific EC2 instances) or tags (e.g., all resources with tag Backup:Daily). Tag-based assignment is powerful because any new resource with the correct tag is automatically included. This step links the policy to the actual resources that will be protected.
4. **Backup Execution** — When the scheduled time arrives, AWS Backup triggers an API call to the source service to create a recovery point. For EBS, it creates a snapshot; for RDS, a DB snapshot; for EFS, an incremental backup. The recovery point is stored in the specified vault. AWS Backup handles the underlying orchestration, including retries on failure.
5. **Monitor and Report** — You can view backup jobs in the AWS Backup console, see their status (success, failed, or running), and drill into details. CloudWatch metrics and events can alert you if a backup fails. CloudTrail logs all API calls. This step is essential for operational visibility, auditing, and troubleshooting.
6. **Restore from a Recovery Point** — When a restore is needed, you navigate to the recovery point in the vault and choose to restore. The restore process launches new resources (e.g., new EBS volume, new RDS instance) and copies data from the backup. You can restore to a different region or account if cross-region or cross-account copies exist. This step completes the data protection cycle.

## Practical mini-lesson

In a real-world IT environment, AWS Backup is often part of a larger data protection strategy. As a professional, you need to understand how to design backup plans that balance cost, performance, and compliance. Start by auditing your AWS resources: what needs backup, what are the recovery point objectives (RPO) and recovery time objectives (RTO)? For example, a production database might need a 1-hour RPO, meaning backups every hour, while a development file system might only need daily backups.

When creating a backup plan, you specify a schedule using cron expressions. A common pattern is a daily schedule at a low-activity time to avoid performance impacts. You set retention to meet legal or business requirements. For instance, daily backups for 30 days, weekly backups for 6 months, and monthly backups for 1 year. This tiered retention can reduce storage costs while still keeping long-term archives.

Lifecycle policies are another key feature. You can move recovery points to cold storage (Amazon S3 Glacier) after a certain number of days. Cold storage is cheaper but has longer restore times (minutes to hours). For emergency restores, you might want some backups in standard storage for fast access. You must understand that moving to cold storage is a one-way transition; you cannot move it back to standard.

Cross-region copies are essential for disaster recovery. When you configure a copy rule, choose a destination region and a separate retention period for the copy. Remember that cross-region copy costs include data transfer fees and storage fees in the destination region. Plan accordingly. Also, if you copy backups to another AWS account, you need to set up appropriate IAM permissions and a backup vault in the target account.

What can go wrong? Common issues include IAM permission misconfigurations. AWS Backup uses a service-linked role, but you may need to attach additional policies if you use cross-account or custom KMS keys. Another issue is exceeding service quotas: by default, you can have up to 100 backup plans per region and up to 1000 recovery points per vault. If you exceed these, backups will fail. You can request limit increases.

Finally, test restores regularly. A backup is only useful if you can restore from it. Set up automated restore testing in a non-production environment. Use AWS Backup’s restore testing feature (when available) or script a process that restores a recovery point to a temporary resource and validates data integrity. This proactive approach catches problems before a real disaster. By mastering these practical aspects, you demonstrate the depth of knowledge expected in senior IT roles.

## Commands

```
aws backup create-backup-plan --backup-plan file://plan.json
```
Creates a backup plan from a JSON configuration file defining rules, schedules, and lifecycle policies.

*Exam note: Tests understanding of backup plan creation using JSON definitions, including schedule expressions and lifecycle transitions to cold storage or expiration.*

```
aws backup create-backup-vault --backup-vault-name MyVault --encryption-key-arn arn:aws:kms:us-east-1:123456789012:key/abc123
```
Creates a backup vault with a specified KMS key for encryption, used to store backup recovery points.

*Exam note: Exams test knowledge of backup vault encryption, KMS integration, and the importance of specifying a custom encryption key for compliance.*

```
aws backup start-backup-job --backup-vault-name MyVault --resource-arn arn:aws:ec2:us-east-1:123456789012:volume/vol-0abcd1234efgh5678 --iam-role-arn arn:aws:iam::123456789012:role/AWSBackupServiceRole
```
Starts an on-demand backup job for a specific EBS volume, tagging it to the specified vault and using a given IAM role.

*Exam note: Frequently tested: understanding of on-demand backups vs. scheduled backups, required IAM role permissions, and resource ARN format for different services like EBS, RDS, or DynamoDB.*

```
aws backup list-recovery-points-by-backup-vault --backup-vault-name MyVault --query "RecoveryPoints[?Status=='COMPLETED']"
```
Lists all completed recovery points in a backup vault using a JMESPath query to filter by status.

*Exam note: Exams check ability to use AWS CLI query filters to manage and audit recovery points, including status checks and deletion of expired or failed backups.*

```
aws backup create-backup-selection --backup-plan-id plan-1234567890abcdef0 --backup-selection file://selection.json
```
Assigns resources (e.g., specific EC2 instances or RDS databases) to a backup plan using a JSON selection file with tags or resource ARNs.

*Exam note: Tests understanding of resource assignment via tags or ARN list, and how backup selection policies integrate with IAM to scope permissions.*

```
aws backup update-recovery-point-lifecycle --backup-vault-name MyVault --recovery-point-arn arn:aws:backup:us-east-1:123456789012:recovery-point:abc123 --lifecycle DeleteAfterDays=30
```
Modifies the lifecycle policy of an existing recovery point to expire after 30 days, moving it to cold storage if configured.

*Exam note: Exams emphasize lifecycle management: moving backups to cold storage (e.g., Glacier) and setting expiration to optimize cost and compliance with retention policies.*

```
aws backup get-backup-plan --backup-plan-id plan-1234567890abcdef0
```
Retrieves the details of an existing backup plan, including its rules and schedule.

*Exam note: Common in troubleshooting scenarios: verifying plan configuration, checking schedule frequency, and ensuring backup rules are correctly applied.*

## Memory tip

Backup plans are like calendars: you set the dates (schedule) and the duration (retention). Vaults are like bank vaults: secure containers that can be locked (Vault Lock).

## FAQ

**Can AWS Backup back up on-premises servers?**

No, AWS Backup is designed for AWS-native resources. To back up on-premises servers, you can use AWS Storage Gateway or AWS DataSync to bring data into AWS, and then use AWS Backup to protect that data.

**Is AWS Backup free?**

No, AWS Backup charges for the storage consumed by recovery points, data transfer for cross-region copies, and any additional restore operations. There is no charge for the service itself, only for the underlying storage and data movement.

**What is the difference between AWS Backup and native EBS snapshots?**

Native EBS snapshots only back up EBS volumes. AWS Backup can orchestrate backups of multiple services including EBS, RDS, EFS, and more, with centralized policies and cross-region copies. Native snapshots are simpler for a single volume, while AWS Backup is for multi-service environments.

**Can I restore a backup from one region to another region?**

Yes, if you have configured a cross-region copy rule in your backup plan, the recovery point is copied to the destination region. You can then restore that copy in the destination region. This is useful for disaster recovery.

**How do I ensure that nobody can delete my backups?**

You can use AWS Backup Vault Lock with compliance mode. Once locked, no one, including root users, can delete recovery points until the retention period expires. Governance mode allows deletion but logs it. For true immutability, use compliance mode.

**Does AWS Backup support incremental backups?**

Yes, for certain services like Amazon EFS and Amazon FSx, AWS Backup performs incremental backups, meaning only changed blocks are saved. For EBS snapshots, the first snapshot is a full copy, and subsequent ones are differential (only changed blocks). For RDS, backups are full snapshots each time.

**Can I restore a single file from an AWS Backup recovery point?**

For some services like Amazon EFS and FSx, you can perform a file-level restore by using the restore to a new file system and then copying the specific file. For EBS snapshots, you typically restore the entire volume. AWS Backup does not natively support granular file restores for all services yet.

## Summary

AWS Backup is a vital service for any IT professional managing data on AWS. It provides a unified, policy-driven approach to backing up a wide range of AWS resources, including EC2 instances, RDS databases, EFS file systems, and more. By using backup plans, vaults, and lifecycle policies, you can automate backups, enforce retention rules, and meet compliance requirements without writing complex scripts. The ability to copy backups across regions and accounts adds a robust layer of disaster recovery.

For certification exams, understanding AWS Backup is essential because it appears in scenario-based, configuration, and troubleshooting questions. You need to know how to design backup plans, use tag-based assignments, leverage Vault Lock for immutability, and differentiate AWS Backup from native services like EBS snapshots or RDS automated backups. Avoid common mistakes like thinking it works for on-premises resources or that it automatically backs up everything.

The key takeaway for exams and real-world practice is this: AWS Backup centralizes data protection, reduces operational overhead, and gives you a single pane of glass for backup management. Master its features, test your restores, and use it as a cornerstone of your cloud data protection strategy. With AWS Backup, you can ensure that your organization’s data is safe, compliant, and recoverable.

---

Practice questions and the full interactive page: https://courseiva.com/glossary/aws-backup