Skip to content

Commit 6756e17

Browse files
authored
Ele 5131 add documentation for adding glue integration (#2032)
* catalog -> governance * add glue docs * BI small docs fixes * small fix to privatelink docs * small fixes * add glue and atlan icons + fix ask us link * doc fix
1 parent cc143f6 commit 6756e17

21 files changed

Lines changed: 355 additions & 16 deletions

File tree

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -97,3 +97,4 @@ venv/
9797

9898
# elementary outputs
9999
edr_target/
100+
dbt_packages/

docs/cloud/integrations/bi/hex.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Make sure you create a Hex Workspace token with read access for all categories a
1313

1414
### Connecting Hex to Elementary
1515

16-
Navigate to the **Account settings > Environments** and choose the environment to which you would like to connect Elementary.
16+
Navigate to the **Account settings > Environments** and choose the environment to which you would like to connect Hex.
1717
Choose the Hex connection and provide the following details to validate and complete the integration.
1818

1919
- **Base URL**: Your Hex workspace URL. For example: `https://app.hex.tech/my-workspace/`

docs/cloud/integrations/bi/power-bi.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Those features will allow Elementary to get all required info for computing the
2525

2626
### Connecting Power BI to Elementary
2727

28-
Navigate to the **Account settings > Environments** and choose the environment to which you would like to connect Elementary.
28+
Navigate to the **Account settings > Environments** and choose the environment to which you would like to connect Power BI.
2929
Choose the Power BI connection and provide the following details to validate and complete the integration.
3030

3131
- **Tenant:** Your Microsoft tenant which is usaully your company's domain. e.g. `my-company.com`

docs/cloud/integrations/bi/sigma.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Make sure you enable 'REST API' privileges for that client.
1313

1414
### Connecting Sigma to Elementary
1515

16-
Navigate to the **Account settings > Environments** and choose the environment to which you would like to connect Elementary.
16+
Navigate to the **Account settings > Environments** and choose the environment to which you would like to connect Sigma.
1717
Choose the Sigma connection and provide the following details to validate and complete the integration.
1818

1919
- **Cloud Provider:** To determine your Sigma cloud provider, Navigate to **Account -> General Settings** under Sigma's **Administration** menu and look for **'Cloud: ...'**. <br/> Should be one of the following:

docs/cloud/integrations/bi/thoughtspot.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ After you connect Thoughtspot, Elementary will automatically and continuously ex
66
This will provide you end-to-end data lineage to understand your downstream dependencies, called exposures.
77

88

9-
### Enable Trusted Authentication on a priviliged user
9+
### Enable Trusted Authentication on a privileged user
1010

1111
For Elementary to access your Thoughtspot instance's API on your behalf of your user, your user should have Trusted Authentication enabled. <br/>
1212
To enable Trusted Authentication on a user, please follow the [official Thoughtspot documentation](https://developers.thoughtspot.com/docs/trusted-auth-secret-key).<br/>
@@ -19,7 +19,7 @@ It is also possible though to integrate with a regular user, just make sure it c
1919

2020
### Connecting Thoughtspot to Elementary
2121

22-
Navigate to the **Account settings > Environments** and choose the environment to which you would like to connect Elementary.
22+
Navigate to the **Account settings > Environments** and choose the environment to which you would like to connect ThoughtSpot.
2323
Choose the Thoughtspot connection and provide the following details to validate and complete the integration.
2424

2525
- **User Name:** The username of the user you want to use to connect to Thoughtspot.

docs/cloud/integrations/dwh/dremio.mdx

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,5 +68,11 @@ Provide the following fields:
6868
- **User:** The email address of the Elementary user.
6969
- **Token:** The token you generated for the Elementary user.
7070

71+
### Connect your metadata store (optional)
72+
73+
If your Dremio sources contains Iceberg tables, you can connect your metadata store (Iceberg catalog) to your environment. This will allow automatically monitoring volume
74+
and freshness of your Iceberg tables (even if they are ingested outside of Dremio).
75+
76+
Currently only [AWS Glue](/cloud/integrations/metadata-layer/glue) is supported, though more metadata integrations are planned.
7177

7278
<OnboardingHelp />
File renamed without changes.
Lines changed: 107 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,107 @@
1+
---
2+
title: "Glue"
3+
---
4+
5+
The AWS Glue integration in Elementary will allow you to automatically monitor volume & freshness anomalies in your Iceberg tables in Glue, by continouously syncing metadata about Iceberg snapshots.
6+
7+
<Note>
8+
If you connected Amazon Athena as your DWH integration - there's no need to add a Glue integration, as the Athena integration already
9+
contains all the required access for Glue.
10+
</Note>
11+
12+
## AWS Setup
13+
14+
### 1. Create Required IAM Policy
15+
16+
First, you'll need to create an IAM policy with the following permissions:
17+
- **GluePermissions**: Enables reading metadata about tables in your Glue catalog.
18+
- **S3IcebergMetadataReadAccess**: Grants access metadata-only access to files of your Iceberg tables. These metadata files contain statistics about Iceberg snapshots,
19+
such as update cadence and row count changes.
20+
21+
Here is an example of a JSON policy:
22+
```json
23+
{
24+
"Version": "2012-10-17",
25+
"Statement": [
26+
{
27+
"Sid": "GluePermissions",
28+
"Effect": "Allow",
29+
"Action": [
30+
"glue:GetTable",
31+
"glue:GetTables"
32+
],
33+
"Resource": "*"
34+
},
35+
{
36+
"Sid": "S3IcebergMetadataReadAccess",
37+
"Effect": "Allow",
38+
"Action": [
39+
"s3:GetObject"
40+
],
41+
"Resource": [
42+
"arn:aws:s3:::your-iceberg-tables-bucket/*metadata.json"
43+
]
44+
}
45+
]
46+
}
47+
```
48+
49+
### 2. Choose Authentication Method
50+
51+
Elementary supports two authentication methods for connecting to Glue:
52+
53+
#### Option 1: AWS Role Authentication (Recommended)
54+
55+
This is the recommended approach as it provides better security and follows AWS best practices. [Learn more about AWS IAM roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html).
56+
57+
1. **Create an IAM Role**:
58+
- Go to AWS IAM Console
59+
- Create a new role
60+
- Select "Another AWS account" as the trusted entity
61+
- Enter Elementary's AWS account ID: `743289191656`
62+
- (Optional but recommended) Enable "Require external ID" and set a value
63+
- Attach the policy created in step 1
64+
65+
2. **Note down the following information**:
66+
- Role ARN
67+
- External ID (if you enabled it) [Learn more about external IDs](https://aws.amazon.com/blogs/security/how-to-use-external-id-when-granting-access-to-your-aws-resources/).
68+
69+
#### Option 2: Access Key Authentication
70+
71+
This method is less secure as it requires permanent credentials. We recommend using AWS Role authentication instead.
72+
73+
1. **Create an IAM User**:
74+
- Go to AWS IAM Console
75+
- Create a new user, that will be used by elementary to connect to Glue
76+
- Enable programmatic access
77+
- Attach the policy created in step 1
78+
79+
2. **Note down the following information**:
80+
- AWS Access Key ID of the new elementary glue user
81+
- AWS Secret Access Key of the new elementary glue user
82+
83+
## Elementary Configuration
84+
85+
Navigate to the **Account settings > Environments** and choose the environment to which you would like to connect AWS Glue.
86+
Under the "Metadata Layer" section, please choose Glue.
87+
88+
### Connection Settings
89+
90+
Regardless of the authentication method you choose, you'll need to provide:
91+
92+
- **Connection Name**: A descriptive name for your connection (e.g. "Datalake"). Needs to be unique if you're adding more than one metadata integration.
93+
- **Region**: The AWS region where your Glue catalog is located
94+
95+
### Authentication Details
96+
97+
Based on your chosen authentication method:
98+
99+
#### If using AWS Role Authentication:
100+
- Select "AWS Role" as the authentication method
101+
- Enter your role ARN
102+
- Enter your external ID (if you enabled it)
103+
104+
#### If using Access Key Authentication:
105+
- Select "Access Key" as the authentication method
106+
- Enter your AWS Access Key ID
107+
- Enter your AWS Secret Access Key

docs/cloud/integrations/security-and-connectivity/aws-privatelink-integration.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,6 @@ In order to set up a PrivateLink connection with Snowflake, please follow the st
5858
* 10.0.2.x
5959
* 10.0.3.x
6060

61-
## Github Enterprise Server
61+
### Github Enterprise Server
6262

6363
Coming soon!

docs/docs.json

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -247,9 +247,15 @@
247247
]
248248
},
249249
{
250-
"group": "Data Catalog",
250+
"group": "Governance",
251251
"pages": [
252-
"cloud/integrations/catalog/atlan"
252+
"cloud/integrations/governance/atlan"
253+
]
254+
},
255+
{
256+
"group": "Metadata Layer",
257+
"pages": [
258+
"cloud/integrations/metadata-layer/glue"
253259
]
254260
},
255261
{

0 commit comments

Comments
 (0)