AWS Security ChangesHomeSearch

AWS redshift documentation change

Service: redshift · 2026-05-13 · Documentation low

File: redshift/latest/mgmt/managing-aws-backup.md

Summary

Expanded no-backup table support notice to include RG clusters alongside RA3 clusters

Security assessment

Administrative update about backup feature coverage. No security vulnerabilities or security features are mentioned or implied in the change.

Diff

diff --git a/redshift/latest/mgmt/managing-aws-backup.md b/redshift/latest/mgmt/managing-aws-backup.md
index 9d43c67d3..0757f5f4b 100644
--- a//redshift/latest/mgmt/managing-aws-backup.md
+++ b//redshift/latest/mgmt/managing-aws-backup.md
@@ -19 +19 @@ Using AWS Backup for Amazon Redshift, you can configure data protection policies
-No-backup tables aren't supported for RA3 provisioned clusters and Amazon Redshift Serverless workgroups. A table marked as no-backup in an RA3 cluster or serverless workgroup is treated as a permanent table that will always be backed up while taking a snapshot, and always restored when restoring from a snapshot. To avoid snapshot costs for no-backup tables, truncate them before taking a snapshot.
+No-backup tables aren't supported for RG or RA3 provisioned clusters and Amazon Redshift Serverless workgroups. A table marked as no-backup in an RG or RA3 cluster or serverless workgroup is treated as a permanent table that will always be backed up while taking a snapshot, and always restored when restoring from a snapshot. To avoid snapshot costs for no-backup tables, truncate them before taking a snapshot.