AWS Security ChangesHomeSearch

AWS lake-formation: Snowflake federation: access delegation modes and IAM least privilege

Service: lake-formation · 2026-11-07 · Documentation medium

File: lake-formation/latest/dg/catalog-federation-snowflake.md · Type: credentials

Summary

Rewrites the Snowflake federated-catalog guide to add two access delegation modes (source-vended vs aws-vended/registered role), concrete OAuth2 settings (workspace URL root, Snowflake token URL, scope session:role:<role>), storing the programmatic access token in Secrets Manager, a Lake Formation auto-created role scoped to a single secret, and guidance to grant DESCRIBE/SELECT on federated databases and tables.

Security assessment

The change is documentation of credential-handling and least-privilege behavior rather than a fix for a specific vulnerability. It explicitly scopes an auto-created IAM role to secretsmanager:GetSecretValue/DescribeSecret/PutSecretValue on only the selected secret, restricts the trust policy to AWS Glue and Lake Formation in the account/Region, tells users to store the Snowflake access token in Secrets Manager (USER_MANAGED_CLIENT_APPLICATION_CLIENT_SECRET), instructs leaving OAuth2 Client ID blank when Snowflake is the OAuth server, and notes the role needs no Amazon S3 permissions in vended-credential mode. These are security-relevant hardening/best-practice guidance (credential custody, blast-radius reduction, explicit catalog/table grants), not a disclosed incident or CVE, so severity is medium.

Evidence

+     * **Create and use a default role** – Lake Formation creates the role when you create the catalog. The console shows the role name, `LakeFormationIRC-<connection-name>-<suffix>`, before you create. The role's permissions policy allows `secretsmanager:GetSecretValue`, `secretsmanager:DescribeSecret`, and `secretsmanager:PutSecretValue` on the selected secret only. Its trust policy lets only AWS Glue and Lake Formation in this account and Region assume the role.

Diff

diff --git a/lake-formation/latest/dg/catalog-federation-snowflake.md b/lake-formation/latest/dg/catalog-federation-snowflake.md
index 2ff6dc3..95f7509 100644
--- a//lake-formation/latest/dg/catalog-federation-snowflake.md
+++ b//lake-formation/latest/dg/catalog-federation-snowflake.md
@@ -11 +11,3 @@ PrerequisitesCreate Federated CatalogConsiderations when integrating with Snowfl
-AWS Glue Data Catalog federates to Snowflake using the OAuth2 credentials of a Snowflake service principal. You can use this federation to connect to Snowflake Horizon and Snowflake Polaris catalogs. This authentication mechanism allows Data Catalog to access the metadata of various objects (such as catalogs, databases, and tables) in your catalog, based on the privileges associated with the service principal. To ensure access to the right objects, it is essential to grant the service principal in Snowflake with the necessary permissions to read metadata of these objects.
+AWS Glue Data Catalog connects to Snowflake using the OAuth2 credentials of a Snowflake service principal. You can use this feature to connect to Snowflake Horizon and Snowflake Polaris catalogs. AWS Glue Data Catalog requires access to the metadata of various objects (such as catalogs, databases, and tables) in your catalog and uses the privileges associated with the service principal. To ensure access to the right objects, it is essential you configure the service principal in Snowflake with the necessary permissions to read metadata of these objects.
+
+AWS Glue Data Catalog supports two access delegation modes, and you can configure the federated catalog to use credentials vended by either Snowflake (source-vended) or the IAM role that Lake Formation uses (aws-vended). In the former mode, Snowflake Horizon issues temporary Amazon S3 credentials scoped to each table, and AWS Lake Formation passes those credentials to your analytics engine. The IAM role you register with Lake Formation doesn't need access to the Amazon S3 buckets that store your Snowflake tables. For a comparison of the two access delegation modes, see [Access delegation modes](./catalog-federation.html#access-delegation-modes).
@@ -14,0 +17,17 @@ AWS Glue Data Catalog federates to Snowflake using the OAuth2 credentials of a S
+Complete these steps in Snowflake and store its access token before you create the federated catalog.
+
+  1. **Grant the Snowflake role access to the data**
+
+Grant the Snowflake role `USAGE` on the database and schema, and `SELECT` on the tables that you want to federate.
+
+  2. **Create an access token**
+
+Create an access token that lets AWS Glue use this role.
+
+  3. **(Optional) Store the token in AWS Secrets Manager**
+
+Store the access credentials in AWS Secrets Manager under the key `USER_MANAGED_CLIENT_APPLICATION_CLIENT_SECRET`. The CLI secret step later in this topic shows the `create-secret` command.
+
+
+
+
@@ -34 +53 @@ You must be a Lake Formation data lake administrator or have `CREATE_CATALOG` pe
-  1. Sign in to the the console and open the Lake Formation console at [https://console.aws.amazon.com/lakeformation/](https://console.aws.amazon.com/lakeformation/).
+  1. Sign in to the console and open the Lake Formation console at [https://console.aws.amazon.com/lakeformation/](https://console.aws.amazon.com/lakeformation/).
@@ -42 +61 @@ You must be a Lake Formation data lake administrator or have `CREATE_CATALOG` pe
-  5. In **Choose data source** step, select Snowflake from the available options.
+  5. In **Choose data source** step, select Snowflake Horizon Catalog from the available options.
@@ -46 +65 @@ You must be a Lake Formation data lake administrator or have `CREATE_CATALOG` pe
-  7. In **catalog details** container, provide a unique name to your AWS Glue federated catalog and enter the name of the existing Snowflake catalog.
+  7. In **catalog details** container, provide a unique name to your AWS Glue federated catalog and enter the name of the existing Snowflake catalog (the Snowflake database name).
@@ -54 +73 @@ You must be a Lake Formation data lake administrator or have `CREATE_CATALOG` pe
-     * Instance URL – The endpoint URL of your existing Snowflake account.
+     * Workspace URL – Enter the account root only, in the form `https://<account>.snowflakecomputing.com`. Don't include the `/polaris/api/catalog` path; the console rejects it.
@@ -58 +77 @@ You must be a Lake Formation data lake administrator or have `CREATE_CATALOG` pe
-     * Token URL – Specify the URL of remote catalog's identity provider.
+     * Token URL – Specify `https://<account>.snowflakecomputing.com/polaris/api/catalog/v1/oauth/tokens`.
@@ -60 +79 @@ You must be a Lake Formation data lake administrator or have `CREATE_CATALOG` pe
-     * OAuth2 Client ID – (Optional) Specify the Client ID of the OAuth2 credential associated with your remote catalog. If you don't provide a client ID, the token request authenticates using only the client secret stored in AWS Secrets Manager.
+     * OAuth2 Client ID – Leave this blank. When Snowflake is the OAuth server, don't provide a client ID; the token request authenticates using only the client secret stored in AWS Secrets Manager.
@@ -64 +83 @@ You must be a Lake Formation data lake administrator or have `CREATE_CATALOG` pe
-     * Token URL Scope – Specify the OAuth scope for authentication.
+     * Token URL Scope – Specify `session:role:<snowflake-role>`.
@@ -68 +87,3 @@ You must be a Lake Formation data lake administrator or have `CREATE_CATALOG` pe
-  10. Create an IAM role that AWS Glue and Lake Formation service principals can use to access secret in AWS Secrets Manager and Amazon S3 locations of remote Iceberg tables respectively. Select the IAM role in the registration dropdown. Refer to step 2 and 3 in following CLI section for IAM policy details.
+  10. Under **Access delegation mode** , choose **Vended credential** to use credentials issued by Snowflake. Choose **Registered role** to have Lake Formation issue credentials using your IAM role.
+
+  11. In **Register Glue connection with Lake Formation** , choose how to provide the IAM role:
@@ -70 +91 @@ You must be a Lake Formation data lake administrator or have `CREATE_CATALOG` pe
-  11. Select Test Connection to test whether your connection properties and IAM role access are configured correctly.
+     * **Create and use a default role** – Lake Formation creates the role when you create the catalog. The console shows the role name, `LakeFormationIRC-<connection-name>-<suffix>`, before you create. The role's permissions policy allows `secretsmanager:GetSecretValue`, `secretsmanager:DescribeSecret`, and `secretsmanager:PutSecretValue` on the selected secret only. Its trust policy lets only AWS Glue and Lake Formation in this account and Region assume the role.
@@ -72 +93 @@ You must be a Lake Formation data lake administrator or have `CREATE_CATALOG` pe
-  12. Select **Next** to review your settings.
+     * **Use an existing role** – Choose a role that you created. For the required policies, see step 2 in Using the AWS CLI, and step 3 if you choose **Registered role**. With **Vended credential** , the role needs access only to the secret (and to the Amazon VPC network interfaces, if you use Amazon VPC). It doesn't need Amazon S3 permissions.
@@ -74 +95,5 @@ You must be a Lake Formation data lake administrator or have `CREATE_CATALOG` pe
-  13. Select **Create Catalog** in review page.
+  12. (Optional) Choose **Run test** to confirm your connection properties and IAM role access are configured correctly. **Run test** isn't available when you use the default role that Lake Formation creates for you or when you are using Amazon VPC to connect to Snowflake.
+
+  13. Select **Next** to review your settings.
+
+  14. Select **Create Catalog** in review page.
@@ -152,0 +178,2 @@ In the following example, replace ``your-secrets-manager-ARN``, ``your-vpc-id``,
+Skip this step if you use vended-credential mode. In that mode, the remote catalog issues the Amazon S3 credentials, so the IAM role doesn't need access to the table data in Amazon S3.
+
@@ -225 +252 @@ The following example uses OAuth2 authentication configuration to create an AWS
-        "INSTANCE_URL": "your-snowflake-account-URL",
+        "INSTANCE_URL": "https://<account>.snowflakecomputing.com",
@@ -227 +254,2 @@ The following example uses OAuth2 authentication configuration to create an AWS
-        "CATALOG_CASING_FILTER": "LOWERCASE_ONLY"
+        "CREDENTIAL_VENDING_MODE": "SOURCE_VENDED",
+        "CATALOG_CASING_FILTER": "UPPERCASE_ONLY"
@@ -233,4 +261 @@ The following example uses OAuth2 authentication configuration to create an AWS
-            "TokenUrl": "your-internal-or-external-token-server-url",
-            "OAuth2ClientApplication": {
-                "UserManagedClientApplicationClientId": "our-client-id"
-            },
+            "TokenUrl": "https://<account>.snowflakecomputing.com/polaris/api/catalog/v1/oauth/tokens",
@@ -238 +263 @@ The following example uses OAuth2 authentication configuration to create an AWS
-                "scope": "all-apis"
+                "scope": "session:role:<snowflake-role>"
@@ -247 +272 @@ The following example uses OAuth2 authentication configuration to create an AWS
-The `OAuth2ClientApplication` field is optional. If you omit it, the token request authenticates using only the client secret stored in AWS Secrets Manager, without sending a client ID.
+Omit `OAuth2ClientApplication`. When Snowflake is the OAuth server, the token request authenticates using only the client secret (the programmatic access token) stored in AWS Secrets Manager, without sending a client ID.
@@ -260,0 +286,4 @@ Replace ``your-glue-connector-arn`` and ``your-IAM-role-ARN-having-LF-access`` w
+###### Note
+
+Register the connection before you create the catalog. Otherwise, `create-catalog` fails with `The data source … is not registered`.
+
@@ -265 +294 @@ After creating an AWS Glue connection object and registering it with Lake Format
-Provide the federated catalog a unique name at ``your-federated-catalog-name``, reference the catalog in Snowflake at ``catalog-name-in-Snowflake``, and input connection name created earlier at ``your-glue-connection-name``.
+Provide a unique name for the federated catalog at `<your-federated-catalog-name>`, reference the Snowflake database at `<catalog-name-in-Snowflake>`, and enter the connection name you created earlier at `<your-glue-connection-name>`.
@@ -268 +297 @@ Provide the federated catalog a unique name at ``your-federated-catalog-name``,
-        --name your-federated-catalog-name \
+      --name <your-federated-catalog-name> \
@@ -271,2 +300,2 @@ Provide the federated catalog a unique name at ``your-federated-catalog-name``,
-            "Identifier": catalog-name-in-Snowflake",
-            "ConnectionName": your-glue-connection-name"
+        "Identifier": "<catalog-name-in-Snowflake>",
+        "ConnectionName": "<your-glue-connection-name>"
@@ -277,0 +307,10 @@ Provide the federated catalog a unique name at ``your-federated-catalog-name``,
+  7. **Grant Lake Formation permissions**
+
+Catalog-level grants don't carry down to federated databases and tables. Grant `DESCRIBE` on the database, and `SELECT` and `DESCRIBE` on the table wildcard, to each principal that queries the catalog.
+
+  8. **Query the federated catalog**
+
+Query the federated catalog from your analytics engine. For example, in Amazon Athena:
+    
+        SELECT * FROM "<federated-catalog>"."<schema>"."<table>" LIMIT 10;
+