AWS redshift: Redshift federated permissions onboarding: rename Glue registration to multi-warehouse
Summary
Rewrites the Redshift federated permissions onboarding guide to rename 'AWS Glue Data Catalog registration' to 'Amazon Redshift multi-warehouse federated permissions' registration, clarifies that CLI registration uses multi-warehouse while Glue Data Catalog registration is a console option requiring extra Data Catalog/Lake Formation setup, and updates CLI examples, console steps, and headings accordingly. No new security controls are introduced.
Security assessment
The diff is a terminology/UX rewrite of registration instructions (Glue Data Catalog -> multi-warehouse federated permissions) plus a note that the Glue Data Catalog method requires additional Data Catalog and Lake Formation setup. It touches identity-propagation and federated-permission concepts but documents no new security feature, fix, or vulnerability; the IdC identity propagation text is unchanged in substance.
Evidence
+Redshift supports creating a new cluster, restoring a cluster from snapshot, or modifying an existing cluster to register it for Amazon Redshift federated permissions. When you register using the AWS CLI, the cluster is registered with Amazon Redshift multi-warehouse federated permissions. Registration with the AWS Glue Data Catalog is available through the Redshift console as another registration method. In both methods you provide a catalog name. To support IdC identity propagation you can specify a Redshift IdC application arn of Lakehouse type to enable IdC identity propagation.
Diff
diff --git a/redshift/latest/dg/federated-permissions-onboarding.md b/redshift/latest/dg/federated-permissions-onboarding.md index 3f83444..0c8cee6 100644 --- a//redshift/latest/dg/federated-permissions-onboarding.md +++ b//redshift/latest/dg/federated-permissions-onboarding.md @@ -15 +15 @@ Amazon Redshift will no longer support the use of Python UDFs after June 30, 202 -Redshift supports creating a new cluster or restoring a cluster from snapshot with AWS Glue Data Catalog (GDC) registration. You can specify the GDC catalog name part of this registration. To support IdC identity propagation you can specify a Redshift IdC application arn of Lakehouse type to enable IdC identity propagation. +Redshift supports creating a new cluster, restoring a cluster from snapshot, or modifying an existing cluster to register it for Amazon Redshift federated permissions. When you register using the AWS CLI, the cluster is registered with Amazon Redshift multi-warehouse federated permissions. Registration with the AWS Glue Data Catalog is available through the Redshift console as another registration method. In both methods you provide a catalog name. To support IdC identity propagation you can specify a Redshift IdC application arn of Lakehouse type to enable IdC identity propagation. @@ -17 +17 @@ Redshift supports creating a new cluster or restoring a cluster from snapshot wi -**Create a new cluster with Glue data catalog registration** +**Create a new cluster** @@ -22 +22 @@ CLI -To automatically register your newly created cluster with Data Catalog, provide the catalog-name that will be used to create and register your Data Catalog. The `redshift-idc-application-arn` parameter is optional - include it if you want to link your cluster with the Redshift IdC Application of type Lakehouse. You can also establish this IdC application association at a later time. +Registering through the AWS CLI registers your newly created cluster with Amazon Redshift multi-warehouse federated permissions. Provide the `catalog-name` to use for the registration. The `redshift-idc-application-arn` parameter is optional - include it if you want to link your cluster with the Redshift IdC Application of type Lakehouse. You can also establish this IdC application association at a later time. @@ -27 +27 @@ To automatically register your newly created cluster with Data Catalog, provide - --catalog-name 'glue-data-catalog-name' \ + --catalog-name 'catalog-name' \ @@ -40 +40 @@ Console - 4. In Register with AWS Glue Data Catalog section, select **Register with Amazon Redshift federated permissions**. + 4. In the registration section, select **Register with Amazon Redshift federated permissions** and choose a registration method: @@ -42 +42,3 @@ Console - * Input a catalog name identifier. + * **Amazon Redshift multi-warehouse** (default): Input a catalog name identifier. + + * **AWS Glue Data Catalog** : Choose to register with the AWS Glue Data Catalog and input a catalog name identifier. This method requires the additional Data Catalog and Lake Formation setup described in [AWS Glue Data Catalog Prerequisites](./federated-permissions-prereqs-glue.html). @@ -51 +53 @@ Console -**Restore a new cluster with AWS Glue Data Catalog registration** +**Restore a new cluster** @@ -56 +58 @@ CLI -To restore a snapshot into a new cluster with AWS Glue Data Catalog integration, provide the catalog-name that will be used to create and register your AWS Glue catalog. The `redshift-idc-application-arn` parameter is optional - include it if you want to link your cluster with the Redshift IdC Application of type Lakehouse. You can also establish this IdC aspplication association at a later time. +Restoring a snapshot into a new cluster through the AWS CLI registers the cluster with Amazon Redshift multi-warehouse federated permissions. Provide the `catalog-name` to use for the registration. The `redshift-idc-application-arn` parameter is optional - include it if you want to link your cluster with the Redshift IdC Application of type Lakehouse. You can also establish this IdC application association at a later time. @@ -61 +63 @@ To restore a snapshot into a new cluster with AWS Glue Data Catalog integration, - --catalog-name 'glue-data-catalog-name' \ + --catalog-name 'catalog-name' \ @@ -75 +77,3 @@ Console - 4. In Register with AWS Glue Data Catalog section, select **Register with Amazon Redshift federated permissions**. + 4. In the registration section, select **Register with Amazon Redshift federated permissions** and choose a registration method: + + * **Amazon Redshift multi-warehouse** (default): Input a catalog name identifier. @@ -77 +81 @@ Console - * Input a catalog name identifier. + * **AWS Glue Data Catalog** : Choose to register with the AWS Glue Data Catalog and input a catalog name identifier. This method requires the additional Data Catalog and Lake Formation setup described in [AWS Glue Data Catalog Prerequisites](./federated-permissions-prereqs-glue.html). @@ -86 +90 @@ Console -**Modify an existing cluster with AWS Glue Data Catalog registration** +**Modify an existing cluster** @@ -88 +92 @@ Console -If your Redshift cluster is already associated to a Redshift IdC Application of type non-lakehouse, the following occurs during AWS Glue Data Catalog registration: +If your Redshift cluster is already associated to a Redshift IdC Application of type non-lakehouse, the following occurs during registration: @@ -100 +104 @@ If your Redshift cluster is already associated to a Redshift IdC Application of - * After registering with AWS Glue Data Catalog, your existing AWS IAM Identity Center federated identities and their owned resources remain unchanged. The namespace associations for these federated identities are also preserved. + * After registering, your existing AWS IAM Identity Center federated identities and their owned resources remain unchanged. The namespace associations for these federated identities are also preserved. @@ -108 +112 @@ CLI -You can use `modify-lakehouse-configuration` command to register your cluster to AWS Glue Data Catalog, the the `catalog-name` is used to create and register your AWS Glue catalog. To support IdC identity propagation, specify the arn of your lakehouse type RedshiftIdcApplication, this requires a Redshift IdC Application of type Lakehouse, please refer to [Create a new Lakehouse type Redshift IdC application: Identity Center Application Configuration for Redshift Warehouse with federated permissions](https://docs.aws.amazon.com/redshift/latest/dg/federated-permissions-prereqs.html#federated-permissions-prereqs-configuration). +Use the `modify-lakehouse-configuration` command to register your cluster with Amazon Redshift multi-warehouse federated permissions. Provide the `catalog-name` to use for the registration. To support IdC identity propagation, specify the arn of your lakehouse type RedshiftIdcApplication. @@ -114 +118 @@ You can use `modify-lakehouse-configuration` command to register your cluster to - --catalog-name 'glue-data-catalog-name' \ + --catalog-name 'catalog-name' \ @@ -125 +129 @@ Console - 3. From the cluster’s details page, select **Register with AWS Glue Data Catalog** from the **Actions** drop-down menu. + 3. From the cluster's details page, select **Register with Amazon Redshift multi-warehouse** from the **Actions** drop-down menu. @@ -127 +131 @@ Console - 4. Select **Register with Amazon Redshift federated permissions** option and + 4. Choose a registration method and complete the registration: @@ -129 +133,3 @@ Console - * Input a catalog name identifier. + * **Amazon Redshift multi-warehouse** (default): Input a catalog name identifier. + + * **AWS Glue Data Catalog** : Choose to register with the AWS Glue Data Catalog and input a catalog name identifier. This method requires the additional Data Catalog and Lake Formation setup described in [AWS Glue Data Catalog Prerequisites](./federated-permissions-prereqs-glue.html). @@ -138 +144 @@ Console -Redshift Serverless enables workgroup-attached Serverless namespaces to register with AWS Glue Data Catalog. Note that your database will restart during this update. +Redshift Serverless enables workgroup-attached Serverless namespaces to register for Amazon Redshift federated permissions. When you register through the AWS CLI, the namespace is registered with Amazon Redshift multi-warehouse federated permissions. Registration with the AWS Glue Data Catalog is available through the Redshift console as another registration method. Note that your database will restart during this update. @@ -140 +146 @@ Redshift Serverless enables workgroup-attached Serverless namespaces to register -If your Redshift Serverless Namespace is already associated to a Redshift IdC Application of type non-lakehouse, the following occurs during Glue Data Catalog registration: +If your Redshift Serverless Namespace is already associated to a Redshift IdC Application of type non-lakehouse, the following occurs during registration: @@ -152 +158 @@ If your Redshift Serverless Namespace is already associated to a Redshift IdC Ap - * After registering with AWS Glue Data Catalog, your existing AWS IAM Identity Center federated identities and their owned resources remain unchanged. The namespace associations for these federated identities are also preserved. + * After registering, your existing AWS IAM Identity Center federated identities and their owned resources remain unchanged. The namespace associations for these federated identities are also preserved. @@ -160 +166 @@ CLI -You can use `update-lakehouse-configuration` command to register your Redshift Serverless namespace to AWS Glue Data Catalog, the `catalog-name` is used to create and register your glue catalog. To support IdC identity propagation, specify the arn of a Redshift Idc Application of type Lakehouse. +Use the `update-lakehouse-configuration` command to register your Redshift Serverless namespace with Amazon Redshift multi-warehouse federated permissions. Provide the `catalog-name` to use for the registration. To support IdC identity propagation, specify the arn of a Redshift Idc Application of type Lakehouse. @@ -166 +172 @@ You can use `update-lakehouse-configuration` command to register your Redshift S - --catalog-name 'glue-data-catalog-name' \ + --catalog-name 'catalog-name' \ @@ -178 +184,3 @@ Console - 3. From the cluster’s details page, select **Register with AWS Glue Data Catalog** from the **Actions** drop-down menu. + 3. From the cluster's details page, select **Register with Amazon Redshift multi-warehouse** from the **Actions** drop-down menu. + + 4. Choose a registration method and complete the registration: @@ -180 +188 @@ Console - 4. Select **Register with Amazon Redshift federated permissions** option and + * **Amazon Redshift multi-warehouse** (default): Input a catalog name identifier. @@ -182 +190 @@ Console - * Input a catalog name identifier. + * **AWS Glue Data Catalog** : Choose to register with the AWS Glue Data Catalog and input a catalog name identifier. This method requires the additional Data Catalog and Lake Formation setup described in [AWS Glue Data Catalog Prerequisites](./federated-permissions-prereqs-glue.html). @@ -197 +205 @@ Amazon Redshift supports Identity Center (IdC) identity propagation to seamlessl - * You have an Amazon Redshift Cluster or Amazon Redshift Serverless Namespace that is registered with AWS Glue Data Catalog. + * You have an Amazon Redshift Cluster or Amazon Redshift Serverless Namespace that is registered for federated permissions. @@ -204 +212 @@ Amazon Redshift supports Identity Center (IdC) identity propagation to seamlessl -If your Redshift Cluster or Redshift Serverless Namespace is already associated to a Redshift IdC Application of type other than Lakehouse, the following occurs during AWS Glue Data Catalog registration: +If your Redshift Cluster or Redshift Serverless Namespace is already associated to a Redshift IdC Application of type other than Lakehouse, the following occurs during registration: @@ -223 +231 @@ If your Redshift Cluster or Redshift Serverless Namespace is already associated -For Amazon Redshift Provisioned Cluster that registered its namespace to AWS Glue Data Catalog, it requires Lakehouse Amazon Redshift IdC Application which doesn’t require explicitly AWS IAM Identity Center Identity user assignment to the application, the IdC users login privilege is managed by CONNECT privilege on the Redshift warehouse. +For Amazon Redshift Provisioned Cluster that registered its namespace for federated permissions, it requires Lakehouse Amazon Redshift IdC Application which doesn't require explicitly AWS IAM Identity Center Identity user assignment to the application, the IdC users login privilege is managed by CONNECT privilege on the Redshift warehouse. @@ -244 +252 @@ Console - 3. From the cluster’s details page, select **Register with AWS Glue Data Catalog** 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. @@ -272 +280 @@ 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. @@ -343 +351 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Prerequisites +AWS Glue Data Catalog Prerequisites