AWS redshift: Fix IAM action name and deregistration steps for Redshift federated permissions
Summary
Corrects the misspelled IAM action `redshift:DregisterNamespace` to `redshift:DeregisterNamespace` in the required-permissions lists, adds a note that additional permissions are needed when deregistering a warehouse registered with AWS Glue Data Catalog, renames headings from 'AWS Glue Data Catalog' to 'Amazon Redshift federated permissions', and fixes the Serverless CLI example to use `aws redshift-serverless update-lakehouse-configuration --namespace-name`.
Security assessment
The change corrects an invalid IAM action name in the documented policy requirements and adds a note about additional permissions required for Glue Data Catalog-registered warehouses. This is IAM permission documentation accuracy, not a fix for a specific vulnerability or incident; no CVE or advisory is referenced.
Evidence
+ * `redshift:DeregisterNamespace`
Diff
diff --git a/redshift/latest/dg/federated-permisisons-offboarding-deregister-catalog.md b/redshift/latest/dg/federated-permisisons-offboarding-deregister-catalog.md index ed9d4cd..a2042ae 100644 --- a//redshift/latest/dg/federated-permisisons-offboarding-deregister-catalog.md +++ b//redshift/latest/dg/federated-permisisons-offboarding-deregister-catalog.md @@ -7 +7 @@ -IAM Policy Requirements for Amazon Redshift Federated Permissions DeregistrationDeregister Redshift from AWS Glue Data CatalogDeregister Redshift Serverless namespace from AWS Glue Data Catalog +IAM Policy Requirements for Amazon Redshift Federated Permissions DeregistrationDeregister Redshift clusterDeregister Redshift Serverless namespace @@ -11 +11 @@ Amazon Redshift will no longer support the use of Python UDFs after June 30, 202 -# Deregister from AWS Glue Data Catalog +# Deregister from Amazon Redshift federated permissions @@ -15 +15 @@ Amazon Redshift will no longer support the use of Python UDFs after June 30, 202 -To deregister your cluster or serverless namespace from AWS Glue Data Catalog, below IAM permissions are required. +To deregister your cluster or serverless namespace, below IAM permissions are required. @@ -21 +21 @@ For Redshift Provisioned Clusters - * `redshift:DregisterNamespace` + * `redshift:DeregisterNamespace` @@ -30 +30 @@ For Redshift Serverless - * `redshift:DregisterNamespace` + * `redshift:DeregisterNamespace` @@ -34,0 +35,2 @@ For Redshift Serverless +If you are deregistering a warehouse that was registered with the AWS Glue Data Catalog, the following additional permissions are required: + @@ -51 +53 @@ For Lake Formation Resource Registration -## Deregister Redshift from AWS Glue Data Catalog +## Deregister Redshift cluster @@ -56 +58 @@ CLI -You can use `modify-lakehouse-configuration` command to deregister your cluster from AWS Glue Data Catalog, if you have IdC provider associated with your cluster, it will put the IdC provider in the cluster to disabled mode. +Use the `modify-lakehouse-configuration` command to deregister your cluster. If you have an IdC provider associated with your cluster, it is put into disabled mode. @@ -70 +72 @@ Console - 3. From the cluster’s details page, select **Deregister from AWS Glue Data Catalog** from the **Actions** drop-down menu and choose **Deregister**. + 3. From the cluster's details page, select **Deregister from Amazon Redshift multi-warehouse** from the **Actions** drop-down menu and choose **Deregister**. @@ -75 +77 @@ Console -## Deregister Redshift Serverless namespace from AWS Glue Data Catalog +## Deregister Redshift Serverless namespace @@ -80 +82 @@ CLI -You can use `update-lakehouse-configuration` command to deregister your Redshift Serverless namespace from AWS Glue Data Catalog, if you have IdC provider associated with your cluster, it will put the IdC provider in the cluster to disabled mode. +Use the `update-lakehouse-configuration` command to deregister your Redshift Serverless namespace. If you have an IdC provider associated with your namespace, it is put into disabled mode. @@ -83,2 +85,2 @@ You can use `update-lakehouse-configuration` command to deregister your Redshift - aws redshift modify-lakehouse-configuration \ - --cluster-identifier 'redshift-cluster' \ + aws redshift-serverless update-lakehouse-configuration \ + --namespace-name 'serverless-namespace-name' \ @@ -94 +96 @@ Console - 3. From the cluster’s details page, select **Deregister from AWS Glue Data Catalog** from the **Actions** drop-down menu and choose **Deregister**. + 3. From the cluster's details page, select **Deregister from Amazon Redshift multi-warehouse** from the **Actions** drop-down menu and choose **Deregister**.