AWS redshift: Simplify no-backup table restore note for pause/resume
Summary
Removes the DC2 exception, stating no-backup tables are restored on resume without the RG/RA3 vs DC2 distinction.
Security assessment
This is a behavioral clarification about snapshot/restore of no-backup tables, not a security control change.
Evidence
- * No-backup tables on the cluster are restored on resume for RG and RA3 instance types. They aren't restored on resume for DC2 instance types. For more information about no-backup tables, see [Excluding tables from snapshots](./working-with-snapshots.html#snapshots-no-backup-tables).
Diff
diff --git a/redshift/latest/mgmt/rs-mgmt-pause-resume-cluster.md b/redshift/latest/mgmt/rs-mgmt-pause-resume-cluster.md index 88271ef..1b35c5c 100644 --- a//redshift/latest/mgmt/rs-mgmt-pause-resume-cluster.md +++ b//redshift/latest/mgmt/rs-mgmt-pause-resume-cluster.md @@ -54 +54 @@ When deciding to pause a cluster, consider the following: - * No-backup tables on the cluster are restored on resume for RG and RA3 instance types. They aren't restored on resume for DC2 instance types. For more information about no-backup tables, see [Excluding tables from snapshots](./working-with-snapshots.html#snapshots-no-backup-tables). + * No-backup tables on the cluster are restored on resume. For more information about no-backup tables, see [Excluding tables from snapshots](./working-with-snapshots.html#snapshots-no-backup-tables).