New release needed?

[famarting]

Describe the bug

Based on this other bug in the aws sdk aws/aws-sdk-go-v2#2370 (comment)

and looking at the release date of the only release in this repo, despite of this repo using github.com/aws/aws-sdk-go-v2 v1.19.0, it seems to me that a new release of this repo updating all the aws sdks libs is needed

Expected Behavior

the function signer.GenerateAuthTokenFromRole should not return the error failed to load credentials: unable to assume role, XXXXXXXXXXX: not found, ResolveEndpointV2

Current Behavior

I was trying the function signer.GenerateAuthTokenFromRole

and I got the error

failed to load credentials: unable to assume role, XXXXXXXXXXX: not found, ResolveEndpointV2

Reproduction Steps

can't describe the reproducer step by step, but it consists of using this library for what it was made for, you need an AWS MSK instance with IAM authentication enabled, then you need an IAM user and an IAM role in order to use all of it combined to call the function signer.GenerateAuthTokenFromRole

Possible Solution

No response

Additional Information/Context

No response

aws-msk-iam-sasl-signer-go Module Versions Used

the only one available 1.0.0

Compiler and Version used

$ go version go version go1.21.0 darwin/arm64

Operating System and version

macos sonoma 14.2

[moohyong]

i want to update this issue

[famarting]

btw I can confirm this was the root cause of my issue, I was able to fix the error not found, ResolveEndpointV2 by manually updating the aws sdk dependencies, so the proper solution should consist of creating a new release of this library

[moohyong]

@famarting how to fix this issue, I found the same problem. update dependencies right?

[famarting]

yes update all the aws sdk dependencies

[moohyong]

@famarting I update all dependencies but not working

Error while sending ApiVersionsRequest to broker [HOST]: failed to load credentials: unable to assume role, [ROLE] operation error STS: AssumeRole, get identity: get credentials: failed to refresh cached credentials, no EC2 IMDS role found, operation error ec2imds: GetMetadata, exceeded maximum number of attempts, 3, 

[famarting]

well, that could be good, that could mean your first issue was fixed, as long as you are not seeing not found, ResolveEndpointV2 then the fix is working.... regarding the new error you are getting idk.