AWS redshift: Move Lake Formation prerequisites to Glue Data Catalog page
Summary
Removes the inline Lake Formation IAM permissions (glue:CreateCatalog, glue:GetCatalog, lakeformation:RegisterResource, RegisterResourceWithPrivilegedAccess, Lake Formation IdC management actions), the Lake Formation identity center configuration sections, and the Lake Formation prerequisites section, replacing them with pointers to a new AWS Glue Data Catalog Prerequisites page. Also narrows the Lakehouse IdC application config to only Redshift:Connect and updates related wording.
Security assessment
This is a documentation reorganization that relocates IAM permission and Lake Formation identity-propagation guidance to a separate page rather than fixing a vulnerability or adding new security guidance. The removed lines list permissions (e.g. lakeformation:RegisterResourceWithPrivilegedAccess) and LakeFormation service integrations, but no specific weakness or incident is addressed, so security impact is limited to documentation of permission requirements.
Evidence
+If you register with the AWS Glue Data Catalog instead of Amazon Redshift multi-warehouse, additional IAM permissions and setup are required. See [AWS Glue Data Catalog Prerequisites](./federated-permissions-prereqs-glue.html).
Diff
diff --git a/redshift/latest/dg/federated-permissions-prereqs.md b/redshift/latest/dg/federated-permissions-prereqs.md index ee1857d..c73e8b6 100644 --- a//redshift/latest/dg/federated-permissions-prereqs.md +++ b//redshift/latest/dg/federated-permissions-prereqs.md @@ -7 +7 @@ -IAM policy requirementsApplication configurationLake Formation prerequisitesNetwork configurationConnect privileges +IAM policy requirementsApplication configurationNetwork configurationConnect privileges @@ -37,17 +37 @@ For Redshift Serverless warehouse to enable Redshift federated permissions: -For AWS Glue Data Catalog integration to create a catalog with Redshift federated permissions: - - * `glue:CreateCatalog` - - * `glue:GetCatalog` - - - - -_For Lake Formation resource registration as one time registration to enable Redshift permission federation from remote warehouse with federated permissions:_ - - * `lakeformation:RegisterResource` - - * `lakeformation:RegisterResourceWithPrivilegedAccess` - - - +If you register with the AWS Glue Data Catalog instead of Amazon Redshift multi-warehouse, additional IAM permissions and setup are required. See [AWS Glue Data Catalog Prerequisites](./federated-permissions-prereqs-glue.html). @@ -74,11 +57,0 @@ _For Amazon Redshift IdC application management:_ -_For Lake Formation IdC application management:_ - - * `lakeformation:CreateLakeFormationIdentityCenterConfiguration` - - * `lakeformation:DescribeLakeFormationIdentityCenterConfiguration` - - * `lakeformation:UpdateLakeFormationIdentityCenterConfiguration` - - - - @@ -89 +62 @@ To establish identity propagation for your analytics workloads, create an Amazon -You can create only one Amazon Redshift IdC application of type Lakehouse per AWS account. This application handles identity propagation across all Redshift warehouses that are integrated with Lake Formation and AWS Glue services. The application can only be used with Redshift warehouses that are registered with the AWS Glue Data Catalog. +You can create only one Amazon Redshift IdC application of type Lakehouse per AWS account. This application handles identity propagation across all Redshift warehouses enabled for federated permissions. @@ -175,7 +147,0 @@ Create your Lakehouse IdC application by specifying the Lakehouse application ty - { - "LakeFormation":[ - { - "LakeFormationQuery":{"Authorization": "Enabled"} - } - ] - }, @@ -193 +159 @@ Create your Lakehouse IdC application by specifying the Lakehouse application ty -This configuration enables trusted identity propagation between Redshift and Lake Formation, allowing users to access data across services using their Identity Center credentials without additional permission assignments. +With this configuration, you can access data in Redshift warehouses using your Identity Center credentials, without additional permission assignments. @@ -206 +172 @@ Console - 5. The Lake Formation and Redshift connect identity propagation integrations are enabled by default. + 5. Leave the Redshift connect identity propagation integration at its default (enabled) setting. @@ -220 +186 @@ CLI -Use the `modify-redshift-idc-application` command to enable both `LakeFormation:query` authorization and `Redshift:Connect` authorization. These integrations are essential for cross-service and cross-cluster IdC identity propagation: +Use the `modify-redshift-idc-application` command to enable `Redshift:Connect` authorization. This integration is essential for cross-cluster IdC identity propagation: @@ -226,7 +191,0 @@ Use the `modify-redshift-idc-application` command to enable both `LakeFormation: - { - "LakeFormation":[ - { - "LakeFormationQuery":{"Authorization": "Enabled"} - } - ] - }, @@ -256,109 +215 @@ Console -**Create Lake Formation identity center configuration** - -Your Lake Formation service requires a dedicated IdC application if one has not been created yet. You must also enable `Redshift:Connect` authorization for the configuration to function properly. - -CLI - - -Use the `create-lake-formation-identity-center-configuration` command to enable `Redshift:Connect` authorization. These integrations are essential for Lake Formation propagates IdC identity to Redshift clusters and Redshift Serverless Namespaces - - - aws lakeformation create-lake-formation-identity-center-configuration \ - --instance-arn <your_idc_instance_arn> \ - --service-integrations '[{ - "Redshift": [{ - "RedshiftConnect": { - "Authorization": "ENABLED" - } - }] - }]' - -Console - - - 1. Sign in to the AWS Management Console, and open the Lake Formation console at [https://console.aws.amazon.com/lakeformation/](https://console.aws.amazon.com/lakeformation/). - - 2. In the left navigation pane, select **IAM Identity Center integration**. - - 3. On the IAM Identity Center integration page you can enable trusted identity propagation for Amazon Redshift connect. Lake Formation propagates identity to downstream based on the effective permissions, so that authorized applications can access data on behalf of users. - - - - -**Update Lake Formation identity center configuration** - -If you had configured Lake Formation IdC application that doesn't have the required service integrations enabled, you can update it to support identity propagation between services and clusters/namespaces. - -CLI - - -Use the `update-lake-formation-identity-center-configuration` command to enable `Redshift:Connect` authorization. These integrations are essential for cross-service and cross-cluster IdC identity propagation: - - - aws lakeformation update-lake-formation-identity-center-configuration \ - --service-integrations '[{ - "Redshift": [{ - "RedshiftConnect": { - "Authorization": "ENABLED" - } - }] - }]' - -Console - - - 1. Sign in to the AWS Management Console, and open the Lake Formation console at [https://console.aws.amazon.com/lakeformation/](https://console.aws.amazon.com/lakeformation/). - - 2. In the left navigation pane, select **IAM Identity Center integration**. - - 3. On the IAM Identity Center integration page you can enable trusted identity propagation for Amazon Redshift connect. Lake Formation propagates identity to downstream based on the effective permissions, so that authorized applications can access data on behalf of users. - - - - -## Lake Formation prerequisites - -Customer need Lake Formation `CREATE_CATALOG` permissions to enable AWS Glue Data Catalog with Amazon Redshift federated permissions. - - 1. If the account belongs to an existing Lake Formation customer, the Lake Formation administrator must explicitly grant CREATE_CATALOG permission to each cluster creator. Use the following sample CLI command: - - aws lakeformation grant-permissions \ - --cli-input-json \ - '{ - "Principal": { - "DataLakePrincipalIdentifier": "<PrincipalArn>" - }, - "Resource": { - "Catalog": {} - }, - "Permissions": [ - "CREATE_CATALOG" - ] - }' - - 2. If the account has never used Lake Formation, verify that Catalog Creators is set to IAMAllowedPrincipals in the Administrative Roles and Tasks page of the Lake Formation console. If not configured, set up a Data Lake Administrator by following the [ Create a data lake administrator](https://docs.aws.amazon.com/lake-formation/latest/dg/initial-lf-config.html#create-data-lake-admin). Alternatively, you can create a Data Lake Administrator with the minimum required policies if you will only use AWS Glue Data Catalog with Amazon Redshift federated permissions. - - { - "Version": "2012-10-17", - "Statement": [ - { - "Sid": "Statement1", - "Effect": "Allow", - "Action": [ - "lakeformation:PutDataLakeSettings", - "lakeformation:GrantPermissions", - "lakeformation:GetDataLakeSettings", - "lakeformation:BatchGrantPermissions", - "lakeformation:ListPermissions" - ], - "Resource": [ - "*" - ] - } - ] - } - - 3. Have the DataLake Admin grant permissions to the IAMAllowedPrincipals to Create Catalog. Access can be granted through the **Grant** button for Catalog Creators in the Administrative Role and Tasks page. - - - +If you register with the AWS Glue Data Catalog instead of Amazon Redshift multi-warehouse, you must also create or update a Lake Formation identity center configuration. See [AWS Glue Data Catalog Prerequisites](./federated-permissions-prereqs-glue.html). @@ -410 +261 @@ Considerations -Onboarding +AWS Glue Data Catalog Prerequisites