AWS redshift documentation change
Summary
Updated AWS Backup integration documentation to include serverless namespaces, added IAM permission requirements, clarified limitations, and enhanced restore operation warnings
Security assessment
Added specific IAM permission requirements (RestoreFromClusterSnapshot/RestoreFromSnapshot) and warnings about destructive restores, which improve security documentation but don't address a specific vulnerability
Diff
diff --git a/redshift/latest/mgmt/managing-aws-backup.md b/redshift/latest/mgmt/managing-aws-backup.md index 13c2cbd03..42ca57fed 100644 --- a//redshift/latest/mgmt/managing-aws-backup.md +++ b//redshift/latest/mgmt/managing-aws-backup.md @@ -7 +7 @@ ConsiderationsLimitationsUsing AWS Backup with Amazon Redshift -# Working with AWS Backup +# AWS Backup integration with Amazon Redshift @@ -11 +11 @@ AWS Backup is a fully managed service that helps you centralize and automate dat -Using AWS Backup for Amazon Redshift, you can configure data protection policies and monitor activity for different Amazon Redshift resources in one place. You can also create and store snapshots on Amazon Redshift provisioned clusters. This lets you automate and consolidate backup tasks that you had to do separately before, without any manual processes. +Using AWS Backup for Amazon Redshift, you can configure data protection policies and monitor activity for different Amazon Redshift resources in one place. You can also create and store snapshots on Amazon Redshift provisioned clusters and serverless namespaces. This lets you automate and consolidate backup tasks that you had to do separately before, without any manual processes. @@ -17 +17 @@ No-backup tables are not supported for RA3 and Serverless. A table marked as no- -A backup, or _recovery point_ , represents the content of a resource, such as an Amazon Redshift cluster, at a specified time. A backup generally refers to the different backups in AWS services, such as Amazon Redshift snapshots. AWS Backup saves backups in backup vaults, which you can organize according to your business needs. The terms _recovery point_ and _backup_ are used interchangeably. For more information about AWS Backup, see [Working with backups](https://docs.aws.amazon.com/aws-backup/latest/devguide/recovery-points.html). +A backup, or _recovery point_ , represents the content of a resource, such as an Amazon Redshift cluster, at a specified time. AWS Backup saves backups in backup vaults, which you can organize according to your business needs. The terms _recovery point_ and _backup_ are used interchangeably. For more information about AWS Backup, see [Backup creation, maintenance, and restore](https://docs.aws.amazon.com/aws-backup/latest/devguide/recovery-points.html) in the _AWS Backup Developer Guide_. @@ -19 +19,3 @@ A backup, or _recovery point_ , represents the content of a resource, such as an -Amazon Redshift is natively integrated with AWS Backup. That lets you define your backup plans and assign Amazon Redshift resources to the backup plans. AWS Backup automates the creation of Amazon Redshift manual snapshots, and securely stores these snapshots in an encrypted backup vault that you designate in your backup plan. For information about vaults, see [Working with backup vaults](https://docs.aws.amazon.com/aws-backup/latest/devguide/vaults.html). In the backup plan, you can define the backup frequency, backup window, lifecycle, or backup vault. For information about backup plans, see [Managing backups using backup plans](https://docs.aws.amazon.com/aws-backup/latest/devguide/about-backup-plans.html). +Amazon Redshift is natively integrated with AWS Backup. That lets you define your backup plans and assign Amazon Redshift resources to the backup plans. AWS Backup automates the creation of Amazon Redshift manual snapshots, and securely stores these snapshots in a backup vault that you designate in your backup plan. For information about vaults, see [Backup vaults](https://docs.aws.amazon.com/aws-backup/latest/devguide/vaults.html) in the _AWS Backup Developer Guide_. In the backup plan, you can define the backup frequency, backup window, lifecycle, or backup vault. For information about backup plans, see [Backup plans](https://docs.aws.amazon.com/aws-backup/latest/devguide/about-backup-plans.html) in the _AWS Backup Developer Guide_. + +For information about creating and restoring Amazon Redshift Serverless snapshots without using AWS Backup, see [Snapshots and recovery points](./serverless-snapshots-recovery-points.html). For information about creating and restoring Amazon Redshift provisioned cluster snapshots without using AWS Backup see [Amazon Redshift snapshots and backups](./working-with-snapshots.html). @@ -25 +27 @@ Amazon Redshift is natively integrated with AWS Backup. That lets you define you - * Limitations + * Limitations for using AWS Backup with Amazon Redshift @@ -36 +38,5 @@ Following are considerations for using AWS Backup with Amazon Redshift: - * AWS Backup for Amazon Redshift is available where both AWS Backup and Amazon Redshift are available in the same AWS Regions. For information on where AWS Backup is available, see [Feature availability by AWS Regions](https://docs.aws.amazon.com/aws-backup/latest/devguide/whatisbackup.html#features-by-region). + * AWS Backup for Amazon Redshift is available where both AWS Backup and Amazon Redshift are available in the same AWS Regions. For information on where AWS Backup is available, see [Amazon Redshift endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/redshift-service.html) in _AWS General Reference_. + + * To get started using AWS Backup, verify that you have met all the prerequisites. For more information, see [Prerequisites](https://docs.aws.amazon.com/aws-backup/latest/devguide/getting-started.html#gs-assumptions) in the _AWS Backup Developer Guide_. + + * Affirmatively opt in to AWS Backup service. Opt-in choices apply to the specific account and AWS Region. If you want to use backups in multiple Regions with a given account, you must opt in to each individual Region with that account. For more information, see [Opt in to managing services with AWS Backup](https://docs.aws.amazon.com/aws-backup/latest/devguide/working-with-supported-services.html#opt-in) in the _AWS Backup Developer Guide_. @@ -38 +44 @@ Following are considerations for using AWS Backup with Amazon Redshift: - * To get started using AWS Backup, verify that you have met all the prerequisites. For more information, see [Prerequisites](https://docs.aws.amazon.com/aws-backup/latest/devguide/getting-started.html#gs-assumptions). + * AWS Backup integration for Amazon Redshift only supports manual snapshots for provisioned clusters and serverless namespaces. @@ -40 +46 @@ Following are considerations for using AWS Backup with Amazon Redshift: - * Affirmatively opt in to AWS Backup service. Opt-in choices apply to the specific account and AWS Region. You might have to opt in to multiple Regions using the same account. For more information, see [Getting started 1: Service Opt-in](https://docs.aws.amazon.com/aws-backup/latest/devguide/service-opt-in.html). + * Once you use AWS Backup to manage snapshot settings, you can't continue to manage manual snapshot settings using Amazon Redshift. Instead, you can continue to manage the settings using an AWS Backup plan. For more information, see [Backup plans](https://docs.aws.amazon.com/aws-backup/latest/devguide/about-backup-plans.html) in the _AWS Backup Developer Guide_. @@ -42 +48 @@ Following are considerations for using AWS Backup with Amazon Redshift: - * From the Amazon Redshift console, you can create manual and automated snapshots. AWS Backup only supports manual snapshots at this time. + * Restoring whole data warehouse snapshots to a serverless namespace is a destructive change. All previously existing data in the target namespace is lost when you restore a data warehouse snapshot to that namespace. This only applies to restoring data warehouse snapshots. Restoring single table snapshots to a namespace doesn’t delete existing data. @@ -44 +50 @@ Following are considerations for using AWS Backup with Amazon Redshift: - * Once you use AWS Backup to manage snapshot settings, you can't continue to manage manual snapshot settings using Amazon Redshift. Instead, you can continue to manage the settings using an AWS Backup plan. For more information, see [Managing backups using backup plans](https://docs.aws.amazon.com/aws-backup/latest/devguide/about-backup-plans.html). + * To restore a snapshot to a provisioned cluster, you need to have an IAM policy with the `RestoreFromClusterSnapshot` permission. To restore a snapshot to a serverless namespace, you need to have an IAM policy with the `RestoreFromSnapshot` permission. These permissions apply to the target data warehouse type, not to source snapshot type. For example, to restore a cluster snapshot to a namespace, you would need the `RestoreFromSnapshot` permission, not `RestoreFromClusterSnapshot`. For more information on managing IAM policies, see [Identity and access management in Amazon Redshift](./redshift-iam-authentication-access-control.html). @@ -49 +55 @@ Following are considerations for using AWS Backup with Amazon Redshift: -## Limitations +## Limitations for using AWS Backup with Amazon Redshift @@ -51 +57 @@ Following are considerations for using AWS Backup with Amazon Redshift: -Following are limitations for using AWS Backup in Amazon Redshift: +Following are limitations for using AWS Backup with Amazon Redshift: @@ -55 +61 @@ Following are limitations for using AWS Backup in Amazon Redshift: - * AWS Backup doesn't support Amazon Redshift Serverless. + * When restoring single tables from a snapshot, you can’t restore from a provisioned cluster snapshot to a serverless namespace or vice versa. You can restore entire snapshots in any configuration. For example, you can restore all of the databases in a provisioned cluster snapshot to a serverless namespace, but you can’t restore a single table from that same snapshot to the same namespace. @@ -62 +68 @@ Following are limitations for using AWS Backup in Amazon Redshift: -To protect resources on your Amazon Redshift provisioned clusters, you can use the AWS Backup console, or programmatically use the AWS Backup API or AWS Command Line Interface (AWS CLI). When you need to recover a resource, you can use either the AWS Backup console or the AWS CLI to find and recover the resource you need. For more information, see [AWS Command Line Interface](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/backup/index.html). +To protect resources on your Amazon Redshift data warehouses, you can use the AWS Backup console, or programmatically use the AWS Backup API or AWS Command Line Interface (AWS CLI). When you need to recover a resource, you can use either the AWS Backup console or the AWS CLI to find and recover the resource you need. For more information, see [AWS Command Line Interface](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/backup/index.html). @@ -66 +72 @@ When using AWS Backup for Amazon Redshift, you can perform the following actions - * Create periodic backups that automatically initiate Amazon Redshift snapshots. Periodic backups are useful to meet your long-term data retention needs. For more information, see [Amazon Redshift backups](https://docs.aws.amazon.com/aws-backup/latest/devguide/redshift-backups.html). + * Create periodic backups that automatically initiate Amazon Redshift snapshots. Periodic backups are useful to meet your long-term data retention needs. For more information, see [Amazon Redshift backups](https://docs.aws.amazon.com/aws-backup/latest/devguide/redshift-backups.html) in the _AWS Backup Developer Guide_. @@ -70 +76 @@ When using AWS Backup for Amazon Redshift, you can perform the following actions - * Restore a cluster to the saved backup you choose. You set how often to back up your resources. For more information, see [Restore an Amazon Redshift cluster](https://docs.aws.amazon.com/aws-backup/latest/devguide/redshift-restores.html). + * Restore a provisioned cluster or serverless namespace to the saved backup you choose. You can choose to restore all of the data in the snapshot or a single table from it. You set how often to back up your resources. For information about restoring provisioned cluster snapshots, see [Restore an Amazon Redshift cluster](https://docs.aws.amazon.com/aws-backup/latest/devguide/redshift-restores.html) in the _AWS Backup Developer Guide_. For information on restoring serverless namespace snapshots, see [ Amazon Redshift Serverless restore ](https://docs.aws.amazon.com/aws-backup/latest/devguide/redshift-serverless-restore.html) in the _AWS Backup Developer Guide_. @@ -81 +87 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Deleting a manual snapshot +Managing resource tags @@ -83 +89 @@ Deleting a manual snapshot -Registering a cluster to the AWS Glue Data Catalog +Cluster versions