Error: invalid AWS access key ID; reason: size should be between 16 and 128 characters, got 1532

[Altiire]

Hello !

I'm trying to setup an AWSConfig to implement tests for my s3 backend.

The access key provided by my IAM component works with the aws cli but does not work k6-jslib-aws with the following error message:

ERRO[0000] Uncaught (in promise) Error: invalid AWS access key ID; reason: size should be between 16 and 128 characters, got 1532
        at apply (native)
        at webpack://k6-jslib-aws/./src/internal/endpoint.ts:4:21(12)
        at r (webpack://k6-jslib-aws/./src/internal/endpoint.ts:4:21(12))
        at construct (native)
        at l (webpack://k6-jslib-aws/./src/internal/endpoint.ts:4:21(24))
        at t (webpack://k6-jslib-aws/./src/internal/config.ts:177:33(14))
        at e (webpack://k6-jslib-aws/./src/internal/config.ts:94:18(97))

cf https://github.com/grafana/k6-jslib-aws/blob/main/src/internal/config.ts#L93

I tried to find a source for the 128 char restriction but I was only able to find a source for the min length of 16.
Do you have a source for more information on why a 128 char restriction is setup here ? If this limitation is was arbitrary setup, are you open to remove it ?

I can provide the following PR.

Regards,

[Altiire]

I found this documentation : https://docs.aws.amazon.com/STS/latest/APIReference/API_Credentials.html

I think the 128 maximum length comes from STS but STS are not mandatory to create an AWSConfig object. I will provide a follow up MR to suggest a fix !

[oleiade]

Hi @Altiire 👋🏻

If my memories don't betray, the main reason for the 128 max limit was to mimic what was at the time set in the official AWS SDK. I wouldn't oppose dropping that limitation if that serve's larger purposes indeed. Which S3-like backend are you targetting if I may ask? 🙇‍♂️

[Altiire]

I don't have the info on the used s3 backend. I agree that my company made IAM can improve the generated ak, and it will be done, but as long as the generated ak/sk works with the official aws cli, I think they should work with k6 lib.

[Altiire]

Hello!
First of all, thank you for merging my PR!
Do you plan to make a new release soon? Otherwise, I’ll need to fork the project until the next release is available. :)

[oleiade]

Hey @Altiire 👋🏻

Indeed I plan to build a new release this week 🙇🏻

[Altiire]

Hello !
Do you have an update on the release date ? 🙏
Regards,

[oleiade]

@Altiire Apologies for the delays, conferences and holidays happened.

We're waiting for a PR to be merged, and once it's done, we'll publish a new release indeed.

In the meantime, if you're in a rush, you could build the bundle files yourselves deno task release and import them in your scripts 🙇🏻