ResolveEndpointV2 error when trying to connect to MSK via IRSA

[scosta-kar]

Creating this issue referencing a bug originally reported in the main dapr repo: dapr/dapr#8122
Issue seems to be a version mismatch in AWS modules

Expected Behavior

PubSub component for kafka (connecting to MSK using IRSA) should just work.

Actual Behavior

time="2024-09-18T17:09:53.885787767Z" level=fatal msg="Fatal error from runtime: process component my-msk-irsa-componen error: [INIT_COMPONENT_FAILURE]: initialization error occurred for my-msk-irsa-componen (pubsub.kafka/v1): [INIT_COMPONENT_FAILURE]: initialization error occurred for my-msk-irsa-componen (pubsub.kafka/v1): error validating iam credentials failed to load credentials: unable to assume role, arn:aws:iam::000000000000:role/my-dapr-role: not found, ResolveEndpointV2\nfailed to load declarative subscriptions: rpc error: code = Canceled desc = context canceled" app_id=my-dapr-app instance=my-dapr-app-7876c8ffb-5l8kx scope=dapr.runtime type=log ver=1.14.4

Steps to Reproduce the Problem

Most likely trying to access MSK using IRSA would result in a repro.

Release Note

RELEASE NOTE:
UPDATE github.com/aws/aws-sdk-go-v2/credentials [v1.17.0]
UPDATE github.com/aws/aws-sdk-go-v2/feature/rds/auth [v1.4.0]
UPDATE github.com/aws/aws-sdk-go-v2/config [v1.27.0]

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[joaocc]

/remove-lifecycle stale

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[joaocc]

/remove-lifecycle stale

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[yaron2]

PR merged aws/aws-msk-iam-sasl-signer-go#22

@famarting is there a code change needed to enable this authentication scenario in the component?

[famarting]

we need to update the aws-msk-iam-sasl-signer-go dependency