You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now when start daprd and app with dynamod state component, and when app tries to read a value from dynamodb state, it fails with following. It dos not honor read credentials from AWS_CREDENTIALS_PROFILES_FILE. If I manually copy creds to ~/.aws/credentials it works fine.
io.dapr.exceptions.DaprException: INTERNAL: fail to get key1 from state store mydynamodb: NoCredentialProviders: no valid providers in chain. Deprecated.
For verbose messaging see aws.Config.CredentialsChainVerboseErrors
at io.dapr.exceptions.DaprException.propagate(DaprException.java:168)
at io.dapr.client.DaprClientGrpc$2.onError(DaprClientGrpc.java:727)
at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:478)
at io.grpc.internal.DelayedClientCall$DelayedListener$3.run(DelayedClientCall.java:463)
The text was updated successfully, but these errors were encountered:
I'm not particularly familiar with the AWS authentication provider in Dapr, but just looking at credential handling suggests that it only works with static credentials provided through the component metadata fields (AccessKey, SecretKey and SessionToken like in dynamodb).
I'm not sure if this would work differently for the underlying aws-go-sdk, but it seems like there would need to be an epic similar to #1103 for Azure; AWS components already do at least all seem to go through the common auth component, but expanding the support to other AWS auth configurations is also probably something that could use contributor help with.
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.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.
Steps to recreate:
In your ~/.aws/config provide a AWS_PROFILE which will do external credential source.(https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-sourcing-external.html)
In my case, it dumps credentials to a custom path directed via AWS_CREDENTIALS_PROFILES_FILE ~/.aws/myorg-credentials
Now when start daprd and app with dynamod state component, and when app tries to read a value from dynamodb state, it fails with following. It dos not honor read credentials from AWS_CREDENTIALS_PROFILES_FILE. If I manually copy creds to ~/.aws/credentials it works fine.
io.dapr.exceptions.DaprException: INTERNAL: fail to get key1 from state store mydynamodb: NoCredentialProviders: no valid providers in chain. Deprecated.
For verbose messaging see aws.Config.CredentialsChainVerboseErrors
at io.dapr.exceptions.DaprException.propagate(DaprException.java:168)
at io.dapr.client.DaprClientGrpc$2.onError(DaprClientGrpc.java:727)
at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:478)
at io.grpc.internal.DelayedClientCall$DelayedListener$3.run(DelayedClientCall.java:463)
The text was updated successfully, but these errors were encountered: