
AWS Backup's logically air-gapped (LAG) vault now supports RDS
This page has been translated by machine translation. View original
Introduction
On November 16, 2026, AWS Backup's logically air-gapped vault (LAG vault) added support for RDS DB instances.
In this article, I tried creating a LAG vault and a backup plan in the Tokyo Region (ap-northeast-1) and assigning a DB instance to the plan.
Setup Steps
The AWS CLI version I used is as follows.
aws --version
aws-cli/2.40.3 Python/3.14.8 Linux/7.2.12-402.asahi.fc44.aarch64+16k update-exe/aarch64.fedora-asahi-remix.44
Creating a LAG vault
A LAG vault is created with a different command from a standard vault. A plan that specifies the LAG vault as the primary destination also requires the name of a standard vault, so I create the standard vault first.
aws backup create-backup-vault --backup-vault-name devio-std-vault --backup-vault-tags Purpose=devio-verify --region ap-northeast-1
Next, I create a LAG vault with a minimum retention period of 7 days and a maximum retention period of 35 days.
aws backup create-logically-air-gapped-backup-vault --backup-vault-name devio-lag-vault --min-retention-days 7 --max-retention-days 35 --backup-vault-tags Purpose=devio-verify --region ap-northeast-1
{
"BackupVaultName": "devio-lag-vault",
"BackupVaultArn": "arn:aws:backup:ap-northeast-1:111122223333:backup-vault:devio-lag-vault",
"CreationDate": "2026-11-18T00:03:42.675000+09:00",
"VaultState": "CREATING"
}
The state immediately after creation is CREATING, and in this case it took about 2 minutes to become AVAILABLE. When I ran describe-backup-vault after it became AVAILABLE, the following items were returned.
{
"VaultType": "LOGICALLY_AIR_GAPPED_BACKUP_VAULT",
"VaultState": "AVAILABLE",
"NumberOfRecoveryPoints": 0,
"Locked": true,
"MinRetentionDays": 7,
"MaxRetentionDays": 35,
"EncryptionKeyType": "AWS_OWNED_KMS_KEY"
}
MinRetentionDays and MaxRetentionDays are the lower and upper limits of the retention period (DeleteAfterDays) that can be set in a plan that specifies the vault as the primary destination.
Plan with the LAG vault as the primary destination
Specify the ARN of the LAG vault in TargetLogicallyAirGappedBackupVaultArn of the rule. Specify the name of the standard vault in TargetBackupVaultName. Save the following JSON as plan-primary.json. Replace <ACCOUNT_ID> with your own account ID.
{
"BackupPlanName": "devio-plan-a1-primary",
"Rules": [
{
"RuleName": "monthly-primary-lag",
"TargetBackupVaultName": "devio-std-vault",
"TargetLogicallyAirGappedBackupVaultArn": "arn:aws:backup:ap-northeast-1:<ACCOUNT_ID>:backup-vault:devio-lag-vault",
"ScheduleExpression": "cron(0 5 1 * ? *)",
"StartWindowMinutes": 60,
"CompletionWindowMinutes": 180,
"Lifecycle": {
"DeleteAfterDays": 14
}
}
]
}
aws backup create-backup-plan --backup-plan file://plan-primary.json --backup-plan-tags Purpose=devio-verify --region ap-northeast-1 --output json
{
"BackupPlanId": "1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
"BackupPlanArn": "arn:aws:backup:ap-northeast-1:111122223333:backup-plan:1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
"CreationDate": "2026-11-18T00:06:18.770000+09:00",
"VersionId": "ZXhhbXBsZS12ZXJzaW9uLWlkLTAwMDEtZXhhbXBsZS12ZXJzaW9u"
}
When I omitted TargetBackupVaultName and specified only the ARN of the LAG vault, the CLI's parameter validation returned the following error before calling the API.
aws: [ERROR]: An error occurred (ParamValidation): Parameter validation failed:
Missing required parameter in BackupPlan.Rules[0]: "TargetBackupVaultName"
When I specified the name of the LAG vault in TargetBackupVaultName, the API rejected it with the following error.
aws: [ERROR]: An error occurred (InvalidRequestException) when calling the CreateBackupPlan operation: A LogicallyAirGappedBackupVault vault type cannot be a target for a backup plan. Choose a different vault type, then retry request.
Plan with the LAG vault as the copy destination
Specify the ARN of the LAG vault in DestinationBackupVaultArn of the rule's CopyActions. Save the following JSON as plan-copy.json.
{
"BackupPlanName": "devio-plan-a2-copy",
"Rules": [{
"RuleName": "monthly-copy-to-lag",
"TargetBackupVaultName": "devio-std-vault",
"ScheduleExpression": "cron(0 5 1 * ? *)",
"StartWindowMinutes": 60,
"CompletionWindowMinutes": 180,
"Lifecycle": { "DeleteAfterDays": 14 },
"CopyActions": [{
"DestinationBackupVaultArn": "arn:aws:backup:ap-northeast-1:<ACCOUNT_ID>:backup-vault:devio-lag-vault",
"Lifecycle": { "DeleteAfterDays": 14 }
}]
}]
}
aws backup create-backup-plan --backup-plan file://plan-copy.json --backup-plan-tags Purpose=devio-verify --region ap-northeast-1 --output json
{
"BackupPlanId": "2b3c4d5e-6f7a-4b8c-9d0e-1f2a3b4c5d6e",
"BackupPlanArn": "arn:aws:backup:ap-northeast-1:111122223333:backup-plan:2b3c4d5e-6f7a-4b8c-9d0e-1f2a3b4c5d6e",
"CreationDate": "2026-11-18T00:06:24.169000+09:00",
"VersionId": "ZXhhbXBsZS12ZXJzaW9uLWlkLTAwMDItZXhhbXBsZS12ZXJzaW9u"
}
Assigning RDS
Save a JSON that specifies the ARN of the DB instance in Resources as selection-rds.json, and assign it to the plan with create-backup-selection.
{
"SelectionName": "devio-sel-b1",
"IamRoleArn": "arn:aws:iam::<ACCOUNT_ID>:role/service-role/AWSBackupDefaultServiceRole",
"Resources": ["arn:aws:rds:ap-northeast-1:<ACCOUNT_ID>:db:devio-nonexistent-db"]
}
aws backup create-backup-selection --backup-plan-id <PLAN_ID> --backup-selection file://selection-rds.json --region ap-northeast-1 --output json
{
"SelectionId": "3c4d5e6f-7a8b-4c9d-8e1f-2a3b4c5d6e7f",
"BackupPlanId": "1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
"CreationDate": "2026-11-18T00:07:15.579000+09:00"
}
According to the AWS Backup documentation, the DB instances that can be stored in a LAG vault are those encrypted with a KMS key you created yourself (a customer managed key) or those that are not encrypted. Please note that there is a restriction that instances encrypted with aws/rds, an AWS managed key, cannot be copied.
Conditions That Are Rejected
Retention period
Using a LAG vault with a minimum retention period of 7 days and a maximum retention period of 35 days, I created plans with the vault as the primary destination while varying the DeleteAfterDays value.
| Retention period (DeleteAfterDays) | Result |
|---|---|
| 6 days | Rejected |
| 7 days | Accepted |
| 35 days | Accepted |
| 36 days | Rejected |
| Not specified | Rejected |
The error returned for every rejection was as follows.
aws: [ERROR]: An error occurred (InvalidParameterValueException) when calling the CreateBackupPlan operation: Lifecycle is incompatible with the retention setting of the logically air-gapped backup vault.
Summary
In the Tokyo Region, I created a backup plan targeting an AWS Backup LAG vault and Amazon RDS, and confirmed that the assignment of a DB instance ARN was accepted.
If you have a requirement to store RDS backups in a form that can be neither deleted nor modified until the defined retention period expires, consider introducing an air gap with a LAG vault.



