AWS redshift: Redshift federated permissions offboarding doc wording and UI label updates
Summary
Updated the prerequisite wording for disabling AWS IAM Identity Center propagation (now requiring registration for federated permissions), fixed apostrophe typos, changed the console action label from 'Edit AWS Glue Data Catalog registration' to 'Edit Amazon Redshift multi-warehouse', and renamed the 'Deregister from AWS Glue Data Catalog' section to 'Deregister from Amazon Redshift federated permissions'.
Security assessment
The changes are documentation clarifications and UI label/typo corrections for the IdC identity propagation offboarding procedure. The prerequisite sentence touches on IAM Identity Center propagation and federated permissions, but no vulnerability, CVE, or new security control is introduced or fixed; the edits only improve accuracy of existing guidance.
Evidence
Before you can disable AWS IAM Identity Center propagation, your Amazon Redshift Cluster or Amazon Redshift Serverless Namespace must be registered for federated permissions and associated with a Lakehouse Redshift IdC Application. An Amazon Redshift Serverless namespace requires a workgroup attached to perform the related operations.
Diff
diff --git a/redshift/latest/dg/federated-permissions-offboarding.md b/redshift/latest/dg/federated-permissions-offboarding.md index 638f730..bc7bb92 100644 --- a//redshift/latest/dg/federated-permissions-offboarding.md +++ b//redshift/latest/dg/federated-permissions-offboarding.md @@ -13 +13 @@ Amazon Redshift will no longer support the use of Python UDFs after June 30, 202 -Before you can disable AWS IAM Identity Center propagation, you must have Amazon Redshift Cluster or Amazon Redshift Serverless Namespace has registered with AWS Glue Data Catalog and associated with a Lakehouse Redshift IdC Application. An Amazon Redshift Serverless namespace requires a workgroup attached to perform the related operations. +Before you can disable AWS IAM Identity Center propagation, your Amazon Redshift Cluster or Amazon Redshift Serverless Namespace must be registered for federated permissions and associated with a Lakehouse Redshift IdC Application. An Amazon Redshift Serverless namespace requires a workgroup attached to perform the related operations. @@ -22 +22 @@ CLI -You can use `modify-lakehouse-configuration` command to disable IdC identity propagation for your clusters with Redshift Federated Permissions, note it doesn’t delete the IdC provider from your cluster but put them into disabled mode. +You can use `modify-lakehouse-configuration` command to disable IdC identity propagation for your clusters with Redshift Federated Permissions, note it doesn't delete the IdC provider from your cluster but put them into disabled mode. @@ -36 +36 @@ Console - 3. From the cluster’s details page, select **Edit AWS Glue Data Catalog registration** from the **Actions** drop-down menu. + 3. From the cluster's details page, select **Edit Amazon Redshift multi-warehouse** from the **Actions** drop-down menu. @@ -48 +48 @@ CLI -You can use `modify-lakehouse-configuration` command to disable IdC identity propagation for your namespace with Redshift Federated Permissions, note it doesn’t delete the IdC provider from your cluster but put them into disabled mode. +You can use `modify-lakehouse-configuration` command to disable IdC identity propagation for your namespace with Redshift Federated Permissions, note it doesn't delete the IdC provider from your cluster but put them into disabled mode. @@ -62 +62 @@ Console - 3. From the namespace’s details page, select **Edit AWS Glue Data Catalog registration** from the **Actions** drop-down menu. + 3. From the namespace's details page, select **Edit Amazon Redshift multi-warehouse** from the **Actions** drop-down menu. @@ -77 +77 @@ Federated user configuration -Deregister from AWS Glue Data Catalog +Deregister from Amazon Redshift federated permissions