docs: Intelligent Compute page for AWS Cloud (preview) by MichaelTansiniSeqera · Pull Request #1565 · seqeralabs/docs

MichaelTansiniSeqera · 2026-06-12T15:28:48Z

Summary

Adds a new standalone intelligent-compute.mdx page under platform-cloud/docs/compute-envs/
Covers: preview admonition, what IC is, IAM permissions (with policy JSON), AWS Cloud CE setup steps, and configuration options (provisioningModel, machineTypes)
Updates cloud-sidebar.json to insert the page after aws-cloud

Status

WIP — pending editorial review and internal sign-off before publish.

Checklist

Editorial review pass
Confirm IAM policy JSON is up to date with latest sched release
Confirm sidebar placement is correct
Add screenshot(s) once UI is final

🤖 Generated with Claude Code

Adds a new standalone page covering the Seqera Intelligent Compute preview feature for AWS Cloud compute environments, including IAM permissions, setup steps, and configuration options. Updates the Cloud sidebar to include the new page after aws-cloud. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

netlify · 2026-06-12T15:28:59Z

✅ Deploy Preview for seqera-docs ready!

Name	Link
🔨 Latest commit	`9e84c4d`
🔍 Latest deploy log	https://app.netlify.com/projects/seqera-docs/deploys/6a3c41245216750009fd4796
😎 Deploy Preview	https://deploy-preview-1565--seqera-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

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

Signed-off-by: MichaelTansiniSeqera <michael.tansini@seqera.io>

- Remove <details> collapse from IAM policy — policy is now always visible and copy-pasteable - Add Resource metrics section explaining Requested/Allocated/Used and how to interpret the gap between them - Add Task and run statuses reference table for troubleshooting Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…rer on GCP When WIF credentials are used for Data Explorer, Platform has no embedded private key and must call the GCP IAM signBlob API to generate presigned URLs. roles/iam.serviceAccountTokenCreator on the SA itself is required for this to succeed. Without it, file viewing and download fail silently with a signing error. Running pipelines is unaffected. Updates both Cloud and Enterprise Google Cloud Batch docs. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Deslop and tidy tables * Remove bold * Update intelligent-compute.mdx Signed-off-by: MichaelTansiniSeqera <michael.tansini@seqera.io> * [automated] Fix code formatting * chore: add 'intelligent compute' to doc-tags-allowed.txt --------- Signed-off-by: MichaelTansiniSeqera <michael.tansini@seqera.io> Co-authored-by: MichaelTansiniSeqera <michael.tansini@seqera.io> Co-authored-by: Seqera Docs Bot <info@seqera.io> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>

Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>

justinegeffen · 2026-06-17T08:37:14Z

run vale

github-actions · 2026-06-17T08:37:25Z

🔍 Running Vale on the changed documentation in this PR…

justinegeffen · 2026-06-17T08:49:09Z

run vale

github-actions · 2026-06-17T08:49:20Z

🔍 Running Vale on the changed documentation in this PR…

christopher-hakkaart · 2026-06-17T08:55:26Z

run vale

github-actions · 2026-06-17T08:55:39Z

🔍 Running Vale on the changed documentation in this PR…

justinegeffen · 2026-06-17T09:03:17Z

run vale

github-actions · 2026-06-17T09:03:31Z

🔍 Running Vale on the changed documentation in this PR…

MichaelTansiniSeqera · 2026-06-22T10:23:03Z

@jonmarti can you re-review the updated PR please

…on to FAILED PREEMPTED is itself terminal. The scheduler retries internally (Spot then On-Demand fallback for spotFirst); when all attempts are exhausted the task stays PREEMPTED, it does not transition to FAILED. Addresses review comment from jonmarti on PR #1565. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Tightens prose on the AWS Intelligent Compute (preview) page and the GCP Workload Identity Federation step 6 in both Cloud and Enterprise copies of the Google Cloud Batch page. Cuts duplicated points and filler adverbs, splits loose connectors, swaps passive constructions for active, and normalizes a few status-table descriptions. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

stefanoboriero · 2026-06-25T10:20:16Z

+
+You need the following:
+
+- Intelligent Compute enabled for your organization by Seqera. Contact your account manager to request access.


It's enabled per workspace, not organization

stefanoboriero · 2026-06-25T10:25:35Z

+## Task and run statuses
+
+Intelligent Compute reports a status for each task and for the run as a whole.
+
+### Task statuses
+
+| Status | Description |
+|--------|-------------|
+| <code style={{whiteSpace: 'nowrap'}}>SUBMITTED</code> | Task is queued or submitted to the compute backend. |
+| <code style={{whiteSpace: 'nowrap'}}>RUNNING</code> | Task is running on a compute instance. |
+| <code style={{whiteSpace: 'nowrap'}}>SUCCEEDED</code> | Task completed with exit code 0. |
+| <code style={{whiteSpace: 'nowrap'}}>FAILED</code> | Task failed. Covers non-retriable execution failures (non-zero exit code, container startup errors) and Spot capacity exhaustion after retries. |
+| <code style={{whiteSpace: 'nowrap'}}>CANCELLED</code> | Task was cancelled by the user. |
+| <code style={{whiteSpace: 'nowrap'}}>PREEMPTED</code> | The Spot instance running this task was reclaimed by AWS. The scheduler retries the task on Spot, then falls back to On-Demand for `spotFirst`. If all retries are exhausted, the task ends as `PREEMPTED`. |
+| <code style={{whiteSpace: 'nowrap'}}>UNSCHEDULABLE</code> | No instance type satisfies the task's placement constraints. This occurs when the requested resources exceed what any available instance type can provide, or when specified instance types are unavailable in the region. Check your **Instance types** configuration and the `cpus` and `memory` directives in the failing process. |
+| <code style={{whiteSpace: 'nowrap'}}>UNKNOWN</code> | Task status cannot be determined, typically because of a transient backend failure. |
+
+### Run statuses
+
+| Status | Description |
+|--------|-------------|
+| <code style={{whiteSpace: 'nowrap'}}>ACTIVE</code> | The run is in progress. |
+| <code style={{whiteSpace: 'nowrap'}}>TERMINATING</code> | The run is shutting down. Final tasks are completing or being cancelled. |
+| <code style={{whiteSpace: 'nowrap'}}>TERMINATED</code> | The run ended normally. |
+| <code style={{whiteSpace: 'nowrap'}}>FAILED</code> | The run failed. |
+| <code style={{whiteSpace: 'nowrap'}}>DANGLING</code> | The Nextflow process stopped sending heartbeats. This typically means the launcher process crashed or lost connectivity. Tasks already dispatched to ECS may still be running. Check CloudWatch logs under `/seqera/sched` for details. |


Aren't these IntelligentCompute internal statused that are not exposed to Cloud customers directly? I believe Cloud end user will only ever see the mapped statuses to the usual Platform statuses

Yes, let's remove these as these are only retrievable via the Sched API

stefanoboriero · 2026-06-25T10:33:00Z

+**How to read the numbers:**
+
+- If **Requested** is much higher than **Allocated**, the scheduler found a more efficient instance shape than your directives implied.
+- If **Allocated** is much higher than **Used**, the task ran with idle headroom.


Should we document that if Allocated == Requested, is probably because no prediction model was configured?

We can add a check

stefanoboriero · 2026-06-25T10:34:07Z

+|--------|--------|-------------------|
+| **Requested** | Pipeline `process` directives | The CPU and memory your pipeline asked for, as written in your `process` directives (for example, `cpus = 4`, `memory = 8 GB`). |
+| **Allocated** | Scheduler decision | The CPU and memory the scheduler assigned to the task container. Intelligent Compute may assign values different from what was requested. It selects the most cost-effective instance shape that satisfies the task's requirements. |
+| **Used** | Nextflow trace data | The CPU and memory the task consumed, measured from the Nextflow trace metrics (`pcpu` × `realtime` for CPU, `peakRss` for memory). Requires Fusion to be enabled. Absent for tasks that did not produce trace data. |


Requires Fusion to be enabled.

Fusion is enabled by default, maybe this is about fusion-tracer that requires the NXF_TRACE_FUSION env var to be set to true? I'd have to check if it's actually needed or the executor sets it for you

I think it's superfluous and we can just delete the sentence

stefanoboriero · 2026-06-25T10:42:42Z

+1. Configure the [Intelligent Compute options](#configuration-options) as needed.
+1. Select **Add**.
+
+Seqera validates credentials and configuration on save. On first use, it provisions the required IAM roles and ECS cluster in your account.


Should we mention that ECS cluster are also taken down after they are no longer needed?

yes, will do

MichaelTansiniSeqera and others added 3 commits June 12, 2026 16:32

Update intelligent-compute.mdx

26cd6d2

Signed-off-by: MichaelTansiniSeqera <michael.tansini@seqera.io>

jonmarti reviewed Jun 12, 2026

View reviewed changes

Comment thread platform-cloud/docs/compute-envs/intelligent-compute.mdx Outdated

jonmarti reviewed Jun 12, 2026

View reviewed changes

Comment thread platform-cloud/docs/compute-envs/intelligent-compute.mdx Outdated

jonmarti reviewed Jun 12, 2026

View reviewed changes

Comment thread platform-cloud/docs/compute-envs/intelligent-compute.mdx Outdated

christopher-hakkaart and others added 2 commits June 16, 2026 16:05

Merge branch 'master' into docs/intelligent-compute-aws-preview

abaa94d

Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>

Merge branch 'master' into docs/intelligent-compute-aws-preview

890439d

Merge branch 'master' into docs/intelligent-compute-aws-preview

326d8fd

Merge branch 'master' into docs/intelligent-compute-aws-preview

dce2ce2

Merge branch 'master' into docs/intelligent-compute-aws-preview

a29e0a6

MichaelTansiniSeqera marked this pull request as ready for review June 22, 2026 10:23

justinegeffen and others added 2 commits June 22, 2026 16:31

Merge branch 'master' into docs/intelligent-compute-aws-preview

8576484

justinegeffen requested a review from jonmarti June 24, 2026 20:41

justinegeffen added 1. Editor review Needs a language review 1. Dev/PM/SME Needs a review by a Dev/PM/SME labels Jun 24, 2026

Merge branch 'master' into docs/intelligent-compute-aws-preview

9e84c4d

stefanoboriero reviewed Jun 25, 2026

View reviewed changes


		You need the following:

		- Intelligent Compute enabled for your organization by Seqera. Contact your account manager to request access.

Uh oh!

Conversation

MichaelTansiniSeqera commented Jun 12, 2026

Summary

Status

Checklist

Uh oh!

netlify Bot commented Jun 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for seqera-docs ready!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

justinegeffen commented Jun 17, 2026

Uh oh!

github-actions Bot commented Jun 17, 2026

Uh oh!

justinegeffen commented Jun 17, 2026

Uh oh!

github-actions Bot commented Jun 17, 2026

Uh oh!

christopher-hakkaart commented Jun 17, 2026

Uh oh!

github-actions Bot commented Jun 17, 2026

Uh oh!

justinegeffen commented Jun 17, 2026

Uh oh!

github-actions Bot commented Jun 17, 2026

Uh oh!

MichaelTansiniSeqera commented Jun 22, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

netlify Bot commented Jun 12, 2026 •

edited

Loading