[5.6] Passes token
configuration value to AWS Client
#24746
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The AWS client accepts a
token
configuration value alongsidekey
andsecret
. This value is optional in most cases but it is required when accessing AWS in some environments, e.g: Lambda. At present the Laravel S3 storage driver and the Laravel SQS connector cannot be used from within a Lambda function because this value is not passed through.Via AwsClient:
This was already fixed for the for the mail manager in #23766
This PR fixes it for the S3 driver and the SQS connector which are the remaining AWS integrations in
laravel/framework
.