Repository navigation
docs(intelligent-compute): EC2 backend instance role is per compute env, match it by pattern - #1910
Merged
Merged
Conversation
…nv, match it by pattern With the EC2 backend strategy the scheduler now keeps one instance role per compute environment and bucket set (seqera-sched-vm-instance-ce-<key>) instead of one per cluster (seqera-sched-vm-instance-clu-<id>), and may remove it after 30 days unused, recreating it under the same name on the next run. - widen the cross-account bucket-policy pattern and the role table from seqera-sched-vm-instance-clu-* to seqera-sched-vm-instance-* - say to match roles by pattern, not an exact role ARN: a recreated role gets a new principal ID that a policy naming the old one no longer matches - fix the "per cluster" wording in the IAM table and the S3 access intro Scheduler change: seqeralabs/sched#1415 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com>
❌ Deploy Preview for seqera-docs failed. Why did it fail? →
|
jonmarti
approved these changes
Sep 29, 2026
christopher-hakkaart
self-requested a review
September 30, 2026 01:08
christopher-hakkaart
approved these changes
Sep 30, 2026
justinegeffen
added
2. Edu reviews complete
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
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
Docs for seqeralabs/sched#1415, which should ship in the same release.
With the
EC2backend strategy, Intelligent Compute now keeps one instance role per compute environment and bucket set (seqera-sched-vm-instance-ce-<key>) instead of one per cluster (seqera-sched-vm-instance-clu-<id>). It may also remove a role after 30 days without use, then recreate it under the same name on the next run.Changes to
platform-cloud/docs/compute-envs/intelligent-compute.mdx:seqera-sched-vm-instance-clu-*becomesseqera-sched-vm-instance-*. A bucket policy still scoped to-clu-*denies the new roles at task runtime.Principal. A recreated role gets a new internal principal ID that a policy naming the old role no longer matches. Customers who used-clu-*should widen it toseqera-sched-vm-instance-*.The Enterprise
aws-cloud.mdpages only carry the compute policy, which is scoped toseqera-sched-*, so they need no change.🤖 Generated with Claude Code