[BUG] InvalidAccessKeyId

[nmoturi]

Describe the bug
After the upgrade from 2.2.3 to 2.2.4, we are seeing a errors in server logs indicating invaild acces key id "InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records."

To Reproduce
Steps to reproduce the behavior:

Configure Flowise with s3 storage

Expected behavior
Need to work with the s3 existing access keys

Screenshots
2025-01-29 02:22:13 [ERROR]: unhandledRejection: The AWS Access Key Id you provided does not exist in our records.
InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records.
at throwDefaultError (/usr/local/lib/node_modules/flowise/node_modules/@smithy/smithy-client/dist-cjs/index.js:867:20)
at /usr/local/lib/node_modules/flowise/node_modules/@smithy/smithy-client/dist-cjs/index.js:876:5
at de_CommandError (/usr/local/lib/node_modules/flowise/node_modules/@aws-sdk/client-s3/dist-cjs/index.js:4935:14)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async /usr/local/lib/node_modules/flowise/node_modules/@smithy/middleware-serde/dist-cjs/index.js:35:20
at async /usr/local/lib/node_modules/flowise/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:483:18
at async /usr/local/lib/node_modules/flowise/node_modules/@smithy/middleware-retry/dist-cjs/index.js:321:38
at async /usr/local/lib/node_modules/flowise/node_modules/@aws-sdk/middleware-flexible-checksums/dist-cjs/index.js:286:18
at async /usr/local/lib/node_modules/flowise/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:109:22
at async /usr/local/lib/node_modules/flowise/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:136:14
at async /usr/local/lib/node_modules/flowise/node_modules/@aws-sdk/middleware-logger/dist-cjs/index.js:33:22

Setup

• Installation [docker`]
• Flowise Version 2.2.4
• OS: Linux]
• Browser [e.g. chrome]

[HenryHengZJ]

can you check on your AWS side? does the key exists, and is it the right key?

[nmoturi]

Hi Henry, Yes the Key exists and it works. It was working with v2.2.3 and it stopped working when upgraded to v2.2.4. Going back to v2.2.3 it started to work again. Thanks, Naran

…

________________________________ From: Henry Heng ***@***.***> Sent: Tuesday, 4 February 2025 7:47 PM To: FlowiseAI/Flowise ***@***.***> Cc: Naran M ***@***.***>; Author ***@***.***> Subject: Re: [FlowiseAI/Flowise] [BUG] InvalidAccessKeyId (Issue #3940) can you check on your AWS side? does the key exists, and is it the right key? — Reply to this email directly, view it on GitHub<#3940 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABZ6YB3VFG7SZ6TINVDF4632OB5DJAVCNFSM6AAAAABWB3BKNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZTGI2DGMJVHE>. You are receiving this because you authored the thread.Message ID: ***@***.***>