docs(aws-cloud): document Seqera Intelligent Compute IAM permissions#1382
Conversation
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.
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
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>
Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Stefano Boriero <stefano.boriero@gmail.com>
|
Has this been aligned to https://github.com/seqeralabs/sched/pull/344? there has been recent changes |
|
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 |
|
Done in 069690b |
christopher-hakkaart
left a comment
There was a problem hiding this comment.
Very minor suggestions. Otherwise, it's looking good.
Note that this will only be added to Cloud and the next Enterprise release.
Co-authored-by: Chris Hakkaart <chris.hakkaart@seqera.io> Signed-off-by: Stefano Boriero <stefano.boriero@gmail.com>
|
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 |
|
Actually what to you think about moving this new section before the
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 |
|
@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 |
|
@stefanoboriero, thank you! Is this in Cloud prod and is it planned for 26.1? |
|
@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. |
gavinelder
left a comment
There was a problem hiding this comment.
This IAM policy was missing
DescribeImages -> Required to get and validate the AMI.
Pass-role on the TowerForge created iam roles.
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>
|
Gavins suggestions have been merged, and I have added admonitions to make it clear that it's private preview. |
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:
seqera-sched-prefix and are torn down automatically.seqera-sched-compute-policy) that must be attached to the IAM user/role used by Seqera, in addition to the base AWS Cloud permissions.seqera-sched-*resources) and which remainResource: "*"(AWS APIs that don't support resource-level permissions).ASGEC2Operations/ASGManagementfor ASG-backed clusters,CostExplorerfor Cost Analysis).Files changed
platform-cloud/docs/compute-envs/aws-cloud.mdplatform-enterprise_docs/compute-envs/aws-cloud.mdThe new section is placed between AWS credential options / Required permissions and Managed Amazon Machine Image (AMI) in both docs.
Test plan
<details>block, JSON syntax highlighting,:::noteadmonition).#required-platform-iam-permissions(cloud) and#required-permissions(enterprise) resolve correctly from the new section's cross-link.seqera-sched-compute-policyshipped with the scheduler.