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
Found the issue. I had vapor in my packages due to a previous attempt on vapor. For some reason, it intercepts the SQS connection and does not indeed have the fix that removes token from the configuration used to build the SqsClient.
Error
Invalid configuration value provided for "token". Expected Aws\Token\TokenInterface|Aws\CacheInterface|array|bool|callable, but got string(872)
This is similar to
aws/aws-sdk-php#2567
brefphp/bref#1330 (closed, tried the provided answer without success)
I'm using a serverless.yml SQS configuration similar to #103 and https://bref.sh/docs/laravel/queues.
I've also tried to use the version in getting-started/serverless.yml that uses
iam
andresources.Queue
to build the infrastructure instead.In both cases I see the queue created correctly in SQS but when I try to dispatch anything (events or jobs) I receive
Invalid configuration value provided for "token". Expected Aws\Token\TokenInterface|Aws\CacheInterface|array|bool|callable, but got string(872)
I've tried to add this line in
queue.sqs
config to no avail.My configuration
queue.php
composer installed packages
Full
serverless.yml
for referenceThe text was updated successfully, but these errors were encountered: