AWS Backup manages backup plans and recovery points for supported AWS resources. These sections explain resource selection, organization policies, copy requirements, vault retention protection, and restore testing.
Plans, vaults, and recovery points
AWS Backup schedules and retains backups for assigned AWS resources. A plan is the timetable, a vaultA container that stores and organizes recovery points. is the storage container, and a recovery pointA saved backup that AWS Backup can use to restore a resource. is the saved backup you can restore.
How it works
- Create a plan with backup rules. Each rule sets the schedule, start windowThe period in which a scheduled backup job is allowed to begin., completion windowThe time allowed for a backup job to finish after it starts., destination vault, and lifecycleThe settings that determine when a backup changes storage tier and expires.. Lifecycle means when a backup changes storage tier or expires.
- Assign resources by type, tagsA key-value label used to select or describe a resource., or individual Amazon Resource Names (ARNs), which identify AWS resources. Tags are key-value labels.
- Choose snapshotsA backup of resource data as captured at a particular time. for the state captured by each backup, or continuous backups for point-in-time recoveryRestoring data to a chosen time within a continuous backup retention period. (PITR), which restores to a chosen time within the retention periodThe length of time a backup is kept before it expires..
- AWS Backup stores recovery points in the vault. For resource types that support incremental backupsA backup that saves changes since earlier backups after an initial full backup., it saves a full backup first and changes afterward. Other types use full backups.
| Rule setting | Meaning |
|---|---|
| Start window | Time allowed for a job to begin |
| Completion window | Time allowed for a started job to finish |
| Lifecycle | Storage transition and deletion timing |
| Copy action | Additional backup in a destination vault |
Exam cues
- If the question says two backup rule start windows overlap, think longer retention, because AWS Backup optimizes overlapping backups under that rule.
- If the question says restore to a chosen time, think continuous backups, because snapshots only preserve captured states.
Remember
- Continuous retention: 1 to 35 days.
- Eligible cold backups must stay cold for at least 90 days. Schedule deletion at least 90 days after transition.
- Backups come from plans or on demand. Most frequent schedule: hourly.
Trap: A vault key does not determine every backup’s encryption. Independently encrypted backups use it; other resources inherit source-service encryption.
From the AWS docs (12)
- A backup plan defines when AWS Backup backs up assigned resources and how long it retains their backups.
- A backup rule specifies a schedule, start and completion windows, target vault, lifecycle, and optional copy actions.
- Backup plan resource assignments can select resource types or use tags and conditions; local assignments can target individual resource ARNs.
- A backup vault is a container that stores and organizes backups, also called recovery points.
- The vault KMS key encrypts backups with independent AWS Backup encryption; other backups inherit encryption from the source service.
- For supported resource types, the first backup is full and later incremental backups contain changes; other resource types use full backups.
- Continuous backups support point-in-time recovery, which restores to a chosen time; snapshot backups restore the captured state.
- Continuous backup retention ranges from 1 to 35 days.
- Backups transitioned to cold storage must remain there for at least 90 days, so deletion must be scheduled at least 90 days after transition.
- When backup rule start windows overlap, AWS Backup optimizes backups using the rule with the longer retention period.
- AWS Backup creates backups automatically through backup plans or manually as on-demand backups.
- A backup rule can run snapshot backups every hour, 12 hours, day, week or month, or on a cron expression as often as hourly.
Cross-account copies
Cross-account copies place AWS Backup recovery pointsA saved backup that AWS Backup can use to restore a resource., or saved backups, in another account in the same organization. They can protect recovery data if the production account is compromised. For standard vaultsA container that stores and organizes recovery points., recovery follows a copy-then-restore sequence.
How it works
- The Organizations management account enables cross-account backup. Confirm that the resource type and Regions support copying.
- Create a non-default destination vault. Its resource policyA policy attached to a resource that specifies who may access it., which controls access to that vault, must allow the source caller to use
backup:CopyIntoBackupVault. - Give the source IAM roleAn AWS identity that a service assumes to perform permitted operations., an identity with backup permissions,
backup:CopyFromBackupVaultandbackup:CopyIntoBackupVaultin its identity policyA policy attached to a caller identity that grants its allowed actions.. - Permit destination-account access to the source customer managed encryption key, whose policy you control. For fully managed resources the destination can use
aws/backupor a customer managed keyAn encryption key whose access policy the customer can manage.; other types require a customer managed key. - Copy the backup, then restore in the destination account.
Exam cues
- If the question says a vault policy allows copying but the operation is denied, think source role permissions and encryption-key access, because the vault policy is only one authorization requirement.
- If the question says restore a standard-vault backup into another account, think copy first, because standard vaults do not provide a direct cross-account restore.
- If the question says a destination account might leave the organization with backups, think a service control policyAn organization policy that limits permissions available to member accounts. (SCP) denying
organizations:LeaveOrganization, because the account retains its copies after departure.
Remember
- Same organization; cross-account backup enabled by the management account.
- The default vault cannot be the destination.
- Backups already in cold storage cannot be copied across accounts.
Trap: The standard-vault copy requirement does not describe every vault. AWS RAM sharing of a logically air-gapped vault permits a receiving account to restore without a preliminary copy.
Copy a supported recovery point between standard vaults in accounts in the same organization.
Start the restore from the destination account copy.
Box details (3)
- Source vault
The source copy role needs permissions to copy out and into the destination vault.
- Destination vault
Its vault policy allows the source caller to copy in. Configure the required key access.
- Restore job
Restore the copied recovery point in the destination account with the required service-linked role.
From the AWS docs (14)
- Standard cross-account backup copies require source and destination accounts in the same AWS Organizations organization.
- Only the Organizations management account can enable or disable AWS Backup cross-account backup.
- The source copy role needs backup:CopyFromBackupVault and backup:CopyIntoBackupVault in its identity policy.
- The destination vault resource policy must allow backup:CopyIntoBackupVault for the source caller.
- A customer managed key encrypting the source resource must allow the destination account to use it for a cross-account copy.
- For fully managed resource types, the destination may use aws/backup or a customer managed key; other resource types require a customer managed key for cross-account copies.
- AWS managed key policies cannot be modified to share access across accounts.
- With standard vaults, copy the backup into the target account before restoring it there.
- The destination for a standard cross-account copy cannot be the default vault.
- AWS Backup does not support cross-account copies of backups in cold storage.
- A destination account retains backups if it leaves the organization; an SCP denying organizations:LeaveOrganization can restrict this.
- A logically air-gapped vault shared with AWS RAM permits restores in a receiving account without first copying the backup into that account.
- Cross-account copy support depends on the resource type and AWS Regions involved.
- A backup copy in another account can protect recovery data if the production account is compromised.
Cross-Region copies and PITR limits
Cross-Region copies keep AWS Backup recovery pointsA saved backup that AWS Backup can use to restore a resource., or saved backups, outside the source Region. A copy of a continuous backup is a snapshotA backup of resource data as captured at a particular time. of the resource, so it does not carry the source’s point-in-time recoveryRestoring data to a chosen time within a continuous backup retention period. (PITR) history.
How it works
- Check copy support for the resource type and both Regions. Choose a destination vaultA container that stores and organizes recovery points. and configure its encryption-key access.
- Add a copy action to the backup rule, or copy an eligible existing snapshot on demand. Continuous backups require a rule copy action; on-demand continuous copies are unsupported.
- For a continuous rule, AWS Backup takes and copies snapshots at the rule frequency. Destination copies restore to their captured state, without PITR.
- The first regional copy is full. Later copies are generally incremental when supported. For EBS, changing the destination vault key causes another full copy.
Exam cues
- If the question says a copied continuous backup must support PITR in another Region, think snapshot limitation, because the copied recovery point has no PITR history.
- If the question says Aurora needs backups in another Region, think supported AWS Backup snapshot copies, because native cross-Region automated snapshot-and-log replication is unsupported for Aurora clusters.
- If the question says a remote Aurora recovery point must be fresh, account for copy time and queues, because a newer snapshot is not available until its copy completes.
- If the question says an RDS copy fails because of persistent database options, think destination option group, because AWS Backup does not transfer a custom option group.
Remember
- Copy support varies by resource and Region.
- Backups already in cold storage cannot be copied across Regions.
- Copies generally use the destination vault key. Copies of unencrypted Aurora, DocumentDB, and Neptune clusters remain unencrypted.
Trap: An Aurora AWS Backup copy and native RDS automated backup replication are different mechanisms. Aurora supports the snapshot-copy path; that copy does not gain PITR.
The continuous rule creates and copies a snapshot at its configured frequency.
The destination restores the snapshot state, without point-in-time recovery.
Box details (3)
- Continuous backup
The source provides point-in-time recovery within its retention period.
- Snapshot copy
A supported rule copy action creates a periodic snapshot without PITR history.
- Restore job
Restore the copied snapshot to the state captured when it was created.
From the AWS docs (13)
- AWS Backup can copy supported backups to other Regions on demand or through backup plan copy actions.
- Cross-Region and cross-account copy support depends on resource type and Region.
- The first copy to a new Region is full; later copies are generally incremental if the service supports incremental backups.
- For EBS, changing the destination vault encryption key causes a full copy; subsequent copies to the same vault and key remain incremental.
- Cross-Region and cross-account copies of resources fully managed by AWS Backup use the destination vault key; a same-account cross-Region copy of a resource such as EBS into an aws/backup vault uses that service's AWS managed key; copies of unencrypted Aurora, DocumentDB and Neptune clusters stay unencrypted.
- A continuous backup rule with a supported copy action produces periodic snapshot copies at the rule frequency.
- Copies of continuous backups do not support point-in-time recovery in the destination.
- AWS Backup does not support on-demand copies of continuous backups.
- Backups in cold storage cannot be copied across Regions.
- Aurora DB clusters do not support native cross-Region automated replication of snapshots and transaction logs.
- AWS Backup supports cross-Region Aurora snapshot copies, including simultaneous cross-account and cross-Region copy.
- Cross-Region Aurora snapshot copies can take hours and RDS can queue copy requests when many are in progress.
- AWS Backup does not transfer a custom RDS option group during cross-Region copy; persistent options require a matching group to exist in the destination.
Vault Lock and air-gapped vaults
VaultA container that stores and organizes recovery points. Lock protects AWS Backup recovery pointsA saved backup that AWS Backup can use to restore a resource. against early deletion or lifecycleThe settings that determine when a backup changes storage tier and expires. changes. Its write-once, read-many model means backups remain readable while their retention periodThe length of time a backup is kept before it expires., the time they must be kept, is enforced.
How it works
- Select governance mode for a lock that authorized users can remove, or compliance mode for an immutable lock after grace timeThe period in which a compliance vault lock can still be changed or removed..
- For compliance mode, set
ChangeableForDaysto give at least 3 days to review the configuration. Omitting that parameter selects governance mode. - For protected backups with direct sharing, use a logically air-gapped vault. It includes compliance-mode lock and stores backups in an AWS Backup service-owned account.
- Share that vault using AWS RAM, which grants other accounts access to the shared resource. Receiving accounts can restore directly, including accounts in another organization.
| Protection | Lock removal | Recovery path |
|---|---|---|
| Standard vault, governance | Authorized users can remove the lock | Standard restore or copy workflow |
| Standard vault, compliance | Immutable after grace time | Standard restore or copy workflow |
| Logically air-gapped vault | Compliance-mode lock built in | Direct restore through RAM sharing |
Exam cues
- If the question says privileged users must not delete backups early, think compliance mode after grace time, because a governance lock can be removed.
- If the question says another organization must restore directly, think a RAM-shared logically air-gapped vault, because it supports that sharing path.
Remember
- Compliance grace time is at least 3 days.
- A logically air-gapped vault defaults to an AWS owned key; a customer managed keyAn encryption key whose access policy the customer can manage. is optional.
- A compliance-locked standard vault can be deleted when empty.
Trap: Governance mode does not prevent every privileged user from removing the lock. Compliance mode becomes immutable after its grace time.
Share the logically air-gapped vault through AWS RAM.
The receiving account restores from the shared recovery point.
Box details (3)
- Air-gapped vault
Backups reside in a service-owned account and the vault has compliance-mode lock built in.
- Resource share
Grant a receiving account access, including an account outside the organization.
- Restore job
Restore from the shared vault without first copying into the receiving account.
From the AWS docs (10)
- AWS Backup Vault Lock enforces write-once, read-many retention by rejecting early recovery point deletion and lifecycle changes.
- A governance-mode vault lock can be removed by a user with sufficient IAM permissions.
- After compliance grace time ends, no user or AWS can remove the lock; recovery points remain until their lifecycle completes.
- Compliance-mode Vault Lock requires at least 3 days of grace time before the lock becomes immutable.
- ChangeableForDays selects compliance mode; omitting it selects governance mode.
- A compliance-locked vault can be deleted when it contains no recovery points.
- A logically air-gapped vault has compliance-mode Vault Lock built in.
- Logically air-gapped vaults use an AWS owned encryption key by default and optionally support a customer managed KMS key.
- AWS RAM can share a logically air-gapped vault with other accounts, including accounts outside the organization, for direct restores.
- Logically air-gapped vault backups are stored in an AWS Backup service-owned account.
Flashcards
Nothing to review here right now. Pick other topics or another filter.
·
All 19 cards as a list
What does an AWS Backup plan define, and how are resources selected?
Rules define the schedule, windows, lifecycle, vault, and optional copies. Resource assignments select types, tags, or individual resource ARNs.
An AWS Backup design needs recovery to a chosen time within the retention period. Which backup type should it use?
Continuous backups for a supported resource type. Snapshot backups restore only their captured state.
Does every AWS Backup recovery point use the encryption key of its vault?
No. Independently encrypted backups use the vault key; other resource types inherit source-service encryption.
What minimum cold-storage residence and continuous-backup retention should an AWS Backup plan account for?
Cold storage requires at least 90 days after transition. Continuous backup retention is 1 to 35 days.
What is the most frequent snapshot schedule an AWS Backup plan rule supports?
Hourly, set as a frequency or with a cron expression. Use an on-demand backup for a one-off copy.
What prerequisites allow a standard AWS Backup cross-account copy?
Use accounts in the same organization, enable cross-account backup from the management account, allow the source role to copy out and in, and allow CopyIntoBackupVault in the destination vault policy. Use a non-default destination vault.
An encrypted AWS Backup cross-account copy fails even though its vault policy permits copying. What key settings should be checked?
Check source key sharing and the destination key type. AWS managed key policies cannot be shared; resource types not fully managed by AWS Backup require customer managed keys for cross-account copies.
Can AWS Backup restore from a standard vault in account A directly into account B?
No. Copy into account B first, then restore there. A shared logically air-gapped vault supports a different restore path.
Why keep AWS Backup copies in a separate account, and how can an organization restrict that account from leaving?
Cross-account copies can protect recovery data if the production account is compromised. An SCP denying organizations:LeaveOrganization restricts departure; an account that leaves retains its backups.
An AWS Backup cross-account copy has an Allow in the destination vault policy but still gets an authorization failure. Which identity permissions should be checked?
The source copy role needs backup:CopyFromBackupVault and backup:CopyIntoBackupVault. The destination Allow does not replace the source identity policy.
A team copies AWS Backup continuous backups to another Region and expects point-in-time recovery there. Is that supported?
No. Supported copy actions create periodic snapshots without destination PITR. Check the resource and Region support before configuring the copy.
An Aurora disaster recovery design proposes native RDS automated backup replication to another Region. What backup-copy approach fits Aurora?
Use supported AWS Backup Aurora snapshot copies. Aurora clusters do not support native cross-Region automated snapshot-and-log replication.
Why might an AWS Backup EBS copy become full after changing the destination encryption key?
Changing the destination vault key causes a full EBS copy. Repeated copies to the same vault and key can remain incremental.
Can AWS Backup create an on-demand cross-Region copy of a continuous backup?
No. Use a supported copy action in a continuous backup rule to create periodic snapshot copies.
An Aurora recovery plan needs a fresh snapshot in another Region. Why must it account for copy delays?
Cross-Region copies can take hours and may queue, delaying the availability of the newer recovery point.
How do governance and compliance modes differ in AWS Backup Vault Lock?
Governance locks can be removed by authorized users. Compliance locks become immutable after grace time of at least 3 days; backups remain protected until their lifecycle completes.
What protects an AWS Backup logically air-gapped vault, and how can another account restore from it?
Built-in compliance-mode Vault Lock and encryption with an AWS owned key by default. AWS RAM sharing allows another account to restore directly; a customer managed key is optional.
An AWS Backup design must reject early backup deletion even by privileged users. Which Vault Lock mode should it use?
Compliance mode after its grace time expires. Governance mode remains removable by users with sufficient IAM permissions.
A team needs to restore AWS Backup data from an account outside its organization without first copying recovery points. Which vault can provide this?
A logically air-gapped vault shared through AWS RAM. Its sharing supports receiving accounts outside the organization.