Note Lake Formation permissions for AWS export pipelines - #153
Open
claude[bot] wants to merge 5 commits into
Open
Note Lake Formation permissions for AWS export pipelines#153claude[bot] wants to merge 5 commits into
claude[bot] wants to merge 5 commits into
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains.
|
| Filename | Overview |
|---|---|
| docs/data-pipelines/integrations/aws-s3.mdx | Adds a cross-reference to the Lake Formation permission guidance for Glue and Redshift Spectrum users. |
| docs/data-pipelines/integrations/redshift-spectrum.mdx | Documents separate database-level CREATE_TABLE and S3 data-location permissions. |
| docs/data-pipelines/old-pipelines/integrations/schematized-aws-pipeline.mdx | Correctly clarifies the distinct scopes of the two Lake Formation grants, resolving the previous finding. |
Reviews (3): Last reviewed commit: "Update IAM permissions note for AWS Lake..." | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Clarified permissions required for Glue Data Catalog governed by AWS Lake Formation.
Clarified IAM permissions requirements for Glue Data Catalog governed by AWS Lake Formation.
Contributor
|
for details on changes - https://linear.app/mixpanel/issue/RUN-337/aws-export-pipeline-ui-shows-active-while-exports-fail |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Michael Herrman · Slack thread
Before: the AWS export-pipeline setup pages (Redshift Spectrum, legacy schematized AWS, S3) document the IAM Glue permissions but never mention AWS Lake Formation. A customer whose Glue Data Catalog is governed by Lake Formation follows the IAM steps, gets those right, and exports still silently fail.
After: each of those pages carries a callout: if your catalog is Lake-Formation-governed, IAM alone isn't enough and you must also grant the Mixpanel role Lake Formation permissions (
CREATE_TABLEon the database + a Data location grant on the registered S3 path), at the database level so a recreated table keeps working.How: added a
<Warning>/<Note>callout toredshift-spectrum.mdxandold-pipelines/integrations/schematized-aws-pipeline.mdx, and a one-line cross-reference<Note>toaws-s3.mdx. Prompted by RUN-337, where a dropped-and-recreated Glue table lost its Lake Formation grants and exports failed while the pipeline showed as active.Generated by Claude Code