Skip to content

Fix no secrets in AWS Batch jobs#6499

Merged
pditommaso merged 2 commits intomasterfrom
fix-no-aws-secrets
Oct 22, 2025
Merged

Fix no secrets in AWS Batch jobs#6499
pditommaso merged 2 commits intomasterfrom
fix-no-aws-secrets

Conversation

@jorgee
Copy link
Contributor

@jorgee jorgee commented Oct 22, 2025

This PR include the secrets to the ContainerProperties builder used for AWS Batch jobs. They were missed during the AWS SDK v2 refactor.

Signed-off-by: jorgee <jorge.ejarque@seqera.io>
@netlify
Copy link

netlify bot commented Oct 22, 2025

Deploy Preview for nextflow-docs-staging canceled.

Name Link
🔨 Latest commit b02bcef
🔍 Latest deploy log https://app.netlify.com/projects/nextflow-docs-staging/deploys/68f8c777bfccf20008cc434e

Signed-off-by: jorgee <jorge.ejarque@seqera.io>
@pditommaso pditommaso added this to the 25.10 milestone Oct 22, 2025
@pditommaso pditommaso merged commit c76c325 into master Oct 22, 2025
24 checks passed
@pditommaso pditommaso deleted the fix-no-aws-secrets branch October 22, 2025 13:01
@just-simon-5
Copy link

Hello!

Can I ask a question on this?

I currently have an AWS job definition defined in terraform containing secrets.

I want to replace this job definition with one created by Nextflow via configuration settings.

I have successfully managed to find most of what I need in the aws configuration documentation however I cannot seem to workout how to tell Nextflow which secret to use.

I imagine having to provide a "name" and "valueFrom" (the latter being an ARN).

I am launching this from Seqera Platform and have configured the launchpad with the correct workspace secrets.

Any guidance would be super helpful!

Thanks,
Simon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants