nf-core / cutandrun

Analysis pipeline for CUT&RUN and CUT&TAG experiments that includes QC, support for spike-ins, IgG controls, peak calling and downstream analysis.
https://nf-co.re/cutandrun
MIT License
79 stars 45 forks source link

The AWS Access Key Id you provided does not exist in our records #250

Open cutleraging opened 1 month ago

cutleraging commented 1 month ago

Description of the bug

Cannot download iGenomes because of Access ID Key invalid

Downloading plugin nf-amazon@2.5.3 ERROR ~ The AWS Access Key Id you provided does not exist in our records. (Service: Amazon S3; Status Code: 403; Error Code: InvalidAccessKeyId; Request ID: 70B59C9A73C18ZKQ; S3 Extended Request ID: NVfXjT3Fl0lvmzWx3ChqlQFCR3HRH7dafjXSRsr0g6p6mJbJbBkZLtTFAwC4gAOij9cSnJn1b4YzkNbt/uzuphxcsy/owhtS; Proxy: null)

-- Check script '/gs/gsfs0/users/rcutler/.nextflow/assets/nf-core/cutandrun/./workflows/cutandrun.nf' at line: 26 or see '.nextflow.log' file for more details

Command used and terminal output

#!/bin/bash
#SBATCH --job-name=cutandtag        # Job name
#SBATCH --mail-type=END,FAIL         # Mail events (NONE, BEGIN, END, FAIL, ALL)
#SBATCH --mail-user=ronald.cutler@einsteinmed.edu    # Where to send mail.  Set this to your email address
#SBATCH --partition=unlimited               # Batch partition: test, quick, ht, normal, unlimited
#SBATCH --time=UNLIMITED          # Wall time limit (days-hrs:min:sec)
#SBATCH --output=cutandtag%j.log    # Path to the standard output and error files relative to the working 
#SBATCH --mem=256GB
#SBATCH --cpus-per-task=24

source /gs/gsfs0/hpc01/rhel8/apps/conda3/etc/profile.d/conda.sh
conda activate nextflow

# update
nextflow self-update
nextflow pull nf-core/cutandrun

# run
nextflow run nf-core/cutandrun -r 3.2.2 -profile singularity -params-file nf-params.json

Relevant files

Archive.zip

System information

Nextflow version - version 24.04.4 build 5917 Hardware - HPC Executor - slurm Container engine - Singularity OS - Linux Version of nf-core/cutandrun - v3.2.2-g6e1125d

chris-cheshire commented 2 weeks ago

Does this still error?