Move lineage AWS IAM permissions into compute env and manual setup pages#1401
Merged
Merged
Conversation
Relocates the lineage-specific AWS IAM policies from the data-lineage page into the appropriate IAM reference pages, so users don't need to visit a separate page to find the full set of permissions required. - AWS Batch and AWS Cloud: add Data lineage (optional) section with Platform integration credentials (SQS + S3 bucket notifications), locked down to <REGION>/<ACCOUNT_ID> for SQS - manual-aws-batch-setup: add lineage S3 policy to the EC2 instance role section for users managing their own roles - data-lineage: replace policy blocks with cross-references to the above pages Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Member
Author
|
ready for review, please check that the service role change makes sense, I haven't touched that part of the docs |
Member
christopher-hakkaart
left a comment
christopher-hakkaart
left a comment
There was a problem hiding this comment.
Please check the meaning is retained.
Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Alberto Chiusole <1922124+bebosudo@users.noreply.github.com>
Member
Author
|
What's the plan for enterprise, will data lineage be released with v26.1? is it already documented in the v26.1 branch? |
Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
…h-setup.mdx Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
justinegeffen
approved these changes
May 13, 2026
Contributor
It's going to be in 26.1 and there's a PR with those doc changes here: #1414. |
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
4 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.
Summary
Addresses the suggestion in #1383 (comment): #1383 (comment)
<REGION>/<ACCOUNT_ID>for SQSTest plan
platform-cloud/docs/compute-envs/aws-batch,aws-cloud,data/data-lineage, andenterprise/advanced-topics/manual-aws-batch-setup#data-lineage-optionalresolve correctly in both compute env pages🤖 Generated with Claude Code