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

**URL:** <https://community.seqera.io/t/the-aws-access-key-id-you-provided-does-not-exist-in-our-records/2601>\
**Category:** Ask for help\
**Tags:** nextflow\
**Created:** [March 4, 2026, 5:34pm UTC](https://community.seqera.io/t/the-aws-access-key-id-you-provided-does-not-exist-in-our-records/2601 "2026-03-04T17:34:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![CARTAS\_ESPINEL\_IRENE](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/cartas_espinel_irene/32/2369_2.png) [@CARTAS\_ESPINEL\_IRENE](https://community.seqera.io/u/CARTAS_ESPINEL_IRENE)\
**Post date:** [March 4, 2026, 5:34pm UTC](https://community.seqera.io/t/the-aws-access-key-id-you-provided-does-not-exist-in-our-records/2601/1 "2026-03-04T17:34:27Z")

</div>

Hi!! i am having to use a test pipeline:

nextflow run nf-core/rnaseq -r 3.23.0 -profile test --outdir ./out/

and i am having this issue “The AWS Access Key Id you provided does not exist in our records”:

 ![Captura desde 2026-03-04 14-27-58](https://europe1.discourse-cdn.com/flex013/uploads/seqera/original/2X/c/c531f49e6b42115754abad45847e4394c3e0a79d.png)

I have installed nextflow following what they said in conda ([Installation — Nextflow documentation](https://www.nextflow.io/docs/latest/install.html))

```auto
conda create --name nf-env bioconda::nextflow

```

So i do not know if i need to install something else, how to do it. I really need help to solve it.

Thank you very much

---

<div class="post-metadata">

**Author:** ![CARTAS\_ESPINEL\_IRENE](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/cartas_espinel_irene/32/2369_2.png) [@CARTAS\_ESPINEL\_IRENE](https://community.seqera.io/u/CARTAS_ESPINEL_IRENE)\
**Post date:** [March 5, 2026, 4:04pm UTC](https://community.seqera.io/t/the-aws-access-key-id-you-provided-does-not-exist-in-our-records/2601/2 "2026-03-05T16:04:49Z")

</div>

Ok, so i just want to let my solution in order anyone else have the same issue and maybe this could help him/her. So in my case, there was a previous access\_key and secret\_key ( **aws configure list** ). So my simple solution was to do: **rm -rf .aws/** and that was all! now it works perfectly…it seems that this previous key was generating some conflict with nextflow when downloading the genomes