Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.

Glue

Grant access to your Glue Catalog so Catalog can read metadata. You need permission to create IAM roles and policies in AWS, and to create a user for Catalog with the roles and policies defined below.

1. If Needed, Whitelist Catalog IP

Here are the fixed IPs:

2. Create Relevant IAM Policies

Create the policy below, granting only metadata access.

warning

Make sure to replace <regions> and <account_id> with your own.

{
"Version": "2022-08-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"glue:GetDatabase",
"glue:GetDatabases",
"glue:GetTable",
"glue:GetTables",
"glue:GetPartition",
"glue:GetPartitions",
"glue:BatchGetPartition",
"glue:SearchTables",
"glue:GetTableVersions",
"glue:GetTableVersion",
"glue:GetUserDefinedFunctions",
"glue:GetUserDefinedFunction"
],
"Resource": [
"arn:aws:glue:<region>:<account_id>:tableVersion/*/*/*",
"arn:aws:glue:<region>:<account_id>:table/*/*",
"arn:aws:glue:<region>:<account_id>:catalog",
"arn:aws:glue:<region>:<account_id>:database/*"
]
},
{
"Effect": "Allow",
"Action": [
"s3:ListBucket",
"s3:GetBucketLocation",
"s3:ListAllMyBuckets"
],
"Resource": [
"*"
]
}
]
}

3. Create a Catalog User

4. Add User Connection Info on Catalog

On Catalog's Glue integration page, add your credentials in the following format:

{
"aws_region": "<your_region>",
"aws_account_id": "<your_account>",
"access_key_id": "<your_key_id>",
"access_key_secret": "<your_secret>"
}