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
I have recently ran into an issue after deploying where it appears that the AWS_SESSION_TOKEN that is set by AWS Lambda is not compatible with the AWS Client resolver.
Invalid configuration value provided for "token". Expected Aws\Token\TokenInterface|Aws\CacheInterface|array|bool|callable, but got string(884) "IQoJb3..." token: (Aws\Token\TokenInterface|Aws\CacheInterface|array|bool|callable) Specifies the token used to authorize requests. Provide an Aws\Token\TokenInterface object, an associative array of "token", and an optional "expiration" key, `false` to use a null token, or a callable token provider used to fetch a token or return null. See Aws\Token\TokenProvider for a list of built-in credentials providers. If no token is provided, the SDK will attempt to load one from the environment.
Temporarily changing the queue to use the database driver has resolved my issue for now. But would be eager to know what has caused this and how I can resolve. Please let me know if you have any questions.
The text was updated successfully, but these errors were encountered:
Description:
PHP: 8.0.25
Laravel: 9.41.0
Bref: 1.7.12
Serverless:
Framework Core: 3.23.0 (local) 3.19.0 (global)
Plugin: 6.2.2
SDK: 4.3.2
Flareapp stacktrace: https://flareapp.io/share/67OvlynP#F72
I have recently ran into an issue after deploying where it appears that the AWS_SESSION_TOKEN that is set by AWS Lambda is not compatible with the AWS Client resolver.
My SQS config looks like this in queue.php:
Temporarily changing the queue to use the database driver has resolved my issue for now. But would be eager to know what has caused this and how I can resolve. Please let me know if you have any questions.
The text was updated successfully, but these errors were encountered: