Skip to content

docs(aws-cloud): document Seqera Intelligent Compute IAM permissions#1382

Merged
christopher-hakkaart merged 27 commits into
masterfrom
docs/aws-cloud-seqera-intelligent-compute
May 15, 2026
Merged

docs(aws-cloud): document Seqera Intelligent Compute IAM permissions#1382
christopher-hakkaart merged 27 commits into
masterfrom
docs/aws-cloud-seqera-intelligent-compute

Conversation

@pditommaso
Copy link
Copy Markdown
Contributor

Summary

Add a new Seqera Intelligent Compute section to the AWS Cloud compute environment docs (cloud + enterprise), documenting the optional capability that offloads Nextflow tasks to a Seqera-managed Amazon ECS cluster, and the additional IAM policy required to enable it.

The new section explains:

  • What Seqera Intelligent Compute does in the AWS Cloud compute environment context (offload tasks from the head EC2 instance to a managed ECS cluster, scaling beyond a single instance while keeping fast startup).
  • That all managed AWS resources use the seqera-sched- prefix and are torn down automatically.
  • The complete IAM policy (seqera-sched-compute-policy) that must be attached to the IAM user/role used by Seqera, in addition to the base AWS Cloud permissions.
  • Which statements are scoped (every action AWS allows to scope by ARN is restricted to seqera-sched-* resources) and which remain Resource: "*" (AWS APIs that don't support resource-level permissions).
  • Which statements are optional (ASGEC2Operations/ASGManagement for ASG-backed clusters, CostExplorer for Cost Analysis).

Files changed

  • platform-cloud/docs/compute-envs/aws-cloud.md
  • platform-enterprise_docs/compute-envs/aws-cloud.md

The new section is placed between AWS credential options / Required permissions and Managed Amazon Machine Image (AMI) in both docs.

Test plan

  • Render preview locally and confirm the new section renders correctly (collapsible <details> block, JSON syntax highlighting, :::note admonition).
  • Confirm in-page anchor #required-platform-iam-permissions (cloud) and #required-permissions (enterprise) resolve correctly from the new section's cross-link.
  • Verify the JSON policy is valid and matches the canonical seqera-sched-compute-policy shipped with the scheduler.

Add a new "Seqera Intelligent Compute" section to the AWS Cloud compute
environment docs (cloud + enterprise) describing the optional capability
that offloads Nextflow tasks to a Seqera-managed Amazon ECS cluster, and
the additional IAM policy required to enable it.

The policy mirrors the seqera-sched compute policy: every action that
AWS allows to be scoped by ARN is restricted to the seqera-sched-*
prefix, with the remaining Resource "*" entries reserved for AWS APIs
that don't support resource-level permissions.
@netlify
Copy link
Copy Markdown

netlify Bot commented May 4, 2026

Deploy Preview for seqera-docs ready!

Name Link
🔨 Latest commit 47c502e
🔍 Latest deploy log https://app.netlify.com/projects/seqera-docs/deploys/6a069962be19b30007be8ec0
😎 Deploy Preview https://deploy-preview-1382--seqera-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Comment thread platform-cloud/docs/compute-envs/aws-cloud.md
The scheduler never calls DeleteSecurityGroup. The security group it
manages has a static name (seqera-sched-ecs) shared across clusters in
the region and is not torn down per-cluster.
@justinegeffen justinegeffen added the do not merge Do not merge until this label is removed label May 4, 2026
Comment thread platform-cloud/docs/compute-envs/aws-cloud.md Outdated
Comment thread platform-cloud/docs/compute-envs/aws-cloud.md Outdated
Comment thread platform-cloud/docs/compute-envs/aws-cloud.md Outdated
justinegeffen and others added 2 commits May 5, 2026 21:50
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>
@stefanoboriero stefanoboriero self-assigned this May 6, 2026
stefanoboriero and others added 3 commits May 8, 2026 14:07
Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io>
Signed-off-by: Stefano Boriero <stefano.boriero@gmail.com>
@pditommaso
Copy link
Copy Markdown
Contributor Author

Has this been aligned to https://github.com/seqeralabs/sched/pull/344? there has been recent changes

@stefanoboriero
Copy link
Copy Markdown
Contributor

It's not aligned with the change in the permission scoping and reshuffling of the permissions around statements, only has the one of the missing permissions as it was raised as missing in a previous comment here #1382 (comment). I will copy paste the new structure from the sched pr to this one

@stefanoboriero
Copy link
Copy Markdown
Contributor

stefanoboriero commented May 8, 2026

Done in 069690b

Copy link
Copy Markdown
Member

@christopher-hakkaart christopher-hakkaart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very minor suggestions. Otherwise, it's looking good.

Note that this will only be added to Cloud and the next Enterprise release.

Comment thread platform-cloud/docs/compute-envs/aws-cloud.md Outdated
Comment thread platform-enterprise_docs/compute-envs/aws-cloud.md Outdated
Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io>
Signed-off-by: Stefano Boriero <stefano.boriero@gmail.com>
@stefanoboriero
Copy link
Copy Markdown
Contributor

Awsome, I see @justinegeffen added a do-not-merge label, just letting you know from the engineering side this is good to go, documented permissions have been tested

@stefanoboriero
Copy link
Copy Markdown
Contributor

Actually what to you think about moving this new section before the Create IAM policy section? Currently we have this page layout

  1. Introduction & Limitation - we explain the rationale behind this CE
  2. Supported Regions
  3. Required IAM permission - here we explain the permissions for a Basic cloud CE
  4. Instruction on how to create IAM policy - Agnostic of it being Basic or Intelligent
  5. Instruction on how to create IAM user - Agnostic of it being Basic or Intelligent
  6. Instruction on how to create IAM role - Agnostic of it being Basic or Intelligent
  7. How credentials can be set in Platform
  8. Intelligent compute section - what is it and what permissions required
  9. AMI and advances options

Reading this top to bottom I feel like we're breaking the flow and jumping back and forth between topics, first we talk about IAM permission requirement for Platform, then instructions on how to create IAM resources, then back to other IAM requirements for Platform.

I'd put the Intelligent Compute section right after the Required Platform IAM ones, so we keep close the two parts where we talk about Platform requirements, and after that explain how to create IAM resources

@christopher-hakkaart
Copy link
Copy Markdown
Member

@stefanoboriero - I see what you're getting at.

I've made a POC of a different structure here: #1411

Let me know what you think

@justinegeffen justinegeffen added 1. Editor review Needs a language review 1. Dev/PM/SME Needs a review by a Dev/PM/SME labels May 12, 2026
@justinegeffen
Copy link
Copy Markdown
Contributor

@stefanoboriero, thank you! Is this in Cloud prod and is it planned for 26.1?

@stefanoboriero
Copy link
Copy Markdown
Contributor

@justinegeffen yes it's in Cloud prod (enabled for internal workspaces only for now) and scheduled to be included in enterprise 26.1

@justinegeffen justinegeffen added 2. Reviews complete Reviews complete. Remove label when confirmed in prod. and removed 1. Editor review Needs a language review 1. Dev/PM/SME Needs a review by a Dev/PM/SME labels May 13, 2026
@justinegeffen
Copy link
Copy Markdown
Contributor

@justinegeffen yes it's in Cloud prod (enabled for internal workspaces only for now) and scheduled to be included in enterprise 26.1

If it's internal workspaces only, should we merge this with a caveat or hold off until 26.1? I'm happy to merge but if customers can't use it we should let them know.

@justinegeffen justinegeffen added the do not merge Do not merge until this label is removed label May 13, 2026
Comment thread platform-cloud/docs/compute-envs/aws-cloud.md
Comment thread platform-enterprise_docs/compute-envs/aws-cloud.md Outdated
Copy link
Copy Markdown
Contributor

@gavinelder gavinelder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This IAM policy was missing

DescribeImages -> Required to get and validate the AMI.
Pass-role on the TowerForge created iam roles.

Comment thread platform-cloud/docs/compute-envs/aws-cloud.md Outdated
Comment thread platform-cloud/docs/compute-envs/aws-cloud.md
Comment thread platform-enterprise_docs/compute-envs/aws-cloud.md
christopher-hakkaart and others added 5 commits May 14, 2026 12:04
Co-authored-by: Gavin <gav.elder@gmail.com>
Signed-off-by: Chris Hakkaart <chris.hakkaart@seqera.io>
Co-authored-by: Gavin <gavin.elder@seqera.io>
Signed-off-by: Chris Hakkaart <chris.hakkaart@seqera.io>
@christopher-hakkaart
Copy link
Copy Markdown
Member

Gavins suggestions have been merged, and I have added admonitions to make it clear that it's private preview.

@christopher-hakkaart christopher-hakkaart merged commit f5bdab1 into master May 15, 2026
5 of 7 checks passed
@christopher-hakkaart christopher-hakkaart deleted the docs/aws-cloud-seqera-intelligent-compute branch May 15, 2026 03:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2. Reviews complete Reviews complete. Remove label when confirmed in prod. do not merge Do not merge until this label is removed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants