FAQs on Airgap Data Protection for RDS Resources

Yes, You can protect NeptuneDB or DocumentDB resources using the RDS Airgap workflow. When defining a backup policy, select RDS as the Resource Type and specify the Resource ID. For more information, see Set up backup policy for RDS Airgap Backup.

This happens when the number of manual RDS snapshots in your AWS account exceeds the allowed quota (typically 100 per account). When an AWS accounts hits this limit, it prevents new snapshot creation. In such cases, you can either request a quota increase from AWS or delete older or non-critical snapshots.

The backup workflow does not copy a snapshot to the air-gapped Cloud, and any local snapshots are treated as the main backup to which the normal retention is applied. The snapshots, thus created, may not being deleted as quickly as expected.

One of the most common causes is when an RDS instance is encrypted with AWS managed KMS keys (AMKs). AWS does not allow copying or sharing of snapshots encrypted with AWS managed keys to other accounts, and the air-gap backup job then fails. For more information, refer to the AWS documentation.

We recommend using Customer managed keys (CMKs) for RDS encryption if you want to leverage airgap backup across accounts and deletion workflows. Airgap copy is not supported on backups of RDS instances encrypted with AWS managed keys.