qzyu999 commented on code in PR #3424: URL: https://github.com/apache/fluss/pull/3424#discussion_r3598193917
########## website/docs/streaming-lakehouse/integrate-data-lakes/catalogs/glue.md: ########## @@ -0,0 +1,167 @@ +--- +title: AWS Glue +sidebar_position: 2 +--- + +# AWS Glue + +## Introduction + +[AWS Glue](https://aws.amazon.com/glue/) is a serverless data integration service that makes it easy to discover, prepare, and combine data for analytics, machine learning, and application development. AWS Glue includes a central metadata repository, known as the AWS Glue Data Catalog, which is fully compatible with Apache Iceberg. + +This guide explains how to configure Fluss to use AWS Glue as its Iceberg catalog. For general Iceberg integration details (table mapping, data types, limitations), see [Iceberg](../formats/iceberg.md). + +## How It Works + +When Fluss is configured with AWS Glue as its Iceberg catalog: + +1. Fluss creates and manages Iceberg database and table metadata directly within the AWS Glue Data Catalog. +2. The [tiering service](maintenance/tiered-storage/lakehouse-storage.md#start-the-datalake-tiering-service) writes data files to Amazon S3 and commits snapshots to the Glue Data Catalog. +3. Any AWS native or external query engine (such as Amazon Athena, Amazon EMR, AWS Glue Jobs, Snowflake, Trino, Flink, or Spark) can discover and query the tiered tables through AWS Glue. + +## Prerequisites + +### AWS IAM Permissions + +Fluss and the tiering service require appropriate IAM permissions to interact with AWS Glue and S3. Below is a minimal IAM policy template: + +```json +{ + "Version": "2012-10-17", + "Statement": [ + { + "Effect": "Allow", + "Action": [ + "glue:CreateDatabase", + "glue:GetDatabase", + "glue:GetDatabases", + "glue:UpdateDatabase", + "glue:DeleteDatabase", + "glue:CreateTable", + "glue:GetTable", + "glue:GetTables", + "glue:UpdateTable", + "glue:DeleteTable" + ], + "Resource": [ + "arn:aws:glue:<region>:<account-id>:catalog", + "arn:aws:glue:<region>:<account-id>:database/*", + "arn:aws:glue:<region>:<account-id>:table/*" + ] Review Comment: Hi @leekeiabstraction, the Copilot suggestion about `table/<db>/<table>` is technically more precise, but `table/*` does work as a wildcard matching all tables across all databases in IAM for Glue. I've added a TIP (c0af314f) recommending users scope to specific databases in production: `table/<your-database>/*`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
