I use

-profile test

to confirm all of my compute environment settings are correct; with version 3.23.0 it fails with

The following invalid input values have been detected:
* --igenomes_base (<s3://ngi-igenomes/igenomes/>): could not validate file format of '<s3://ngi-igenomes/igenomes/>': Access Denied (Service: S3, Status Code: 403, Request ID: ...) (SDK Attempt Count: 1)
-- Check script '.nextflow/assets/nf-core/rnaseq/subworkflows/nf-core/utils_nfschema_plugin/main.nf' at line: 68

Works fine with 3.21.0, so I don't think it is actually an S3 issue, rather something wrong with validation in nf-schema

I feel like we fixed that somewhere else

It's this issue: https://github.com/nextflow-io/nf-schema/issues/204 I'll make sure to deploy the fix

Thanks, will look through these! I am not running offline

Yep, this is the fix: https://github.com/nf-core/rnaseq/pull/1745

Oh and to be clear, I do have valid AWS credentials, I am not sure why the 403

Yeah, it's something about accessing 'free' buckets when you're also using authenticated ones

--no-sign-request

or equivalent

might also be fixable like https://nfcore.slack.com/archives/CGRTMASKY/p1719321841024749?thread_ts=1719319577.070789&cid=CGRTMASKY

should we add this to the TEMPLATE?

For my use case, it is only the

<s3://ngi-igenomes>

bucket that should use `--no-sign-request`/`anonymous` config, all other buckets are private

Made the same fix on #C05785S3TMX @Felix Krueger: https://github.com/nf-core/riboseq/pull/151

in #CGFUX04HZ and #C01NHS4CC91 there's

<s3://annotation-cache>

as well

good call

New run from that branch works for me, thanks!