Lambda support by passing on 'token' from configuration to credentials

[danniehansen]

Hi,

This simple fix, fixes an issue when running this SQS FIFO package on Lambda using something like https://github.com/brefphp/laravel-bridge

When working in Lambda you typically assign privileges to the Lambda function it-self. This means instead of receiving a access key id & secret the Lambda instance have temporary tokens that it pass on to the SDK for authentication. So passing on this token from the configuration side of things allows it to authenticate.

With this you'll be able to run server-less Lambda SQS FIFO handlers.

[mnapoli]

👍 on this, here is a link to the corresponding Laravel issue: laravel/laravel#5138 (comment)

Basically this token is part of the AWS credentials in some systems (including AWS Lambda), it is necessary to make it work.

[patrickcarlohickman]

Awesome. Thank you for the PR and both of you for the explanation and context.

[patrickcarlohickman]

One more piece: PR for Laravel SQS connector - laravel/framework#24746

[patrickcarlohickman]

Also laravel/framework#23766, with an explanation that everything should still work fine if the token key is not found.

[mnapoli]

Awesome!

[patrickcarlohickman]

I've tagged a new release with the change (1.2.0). Thanks again!