Hi guys,

Laravel team member here offering an AWS Facade to bring usage of the SDK more inline with Laravel's beautiful syntax. A simple change, but may seem more familiar to users of the framework.

$s3 = AWS::get('s3');

Test is included, and the README has been updated accordingly.

Thanks for the Laravel specific package, and all the great AWS services!

Dayle.

I avoid the use of Facades in my application as much as possible, leveraging Laravels IoC/DI capabilities to load classes throughout my application. This change would more easily facilitate that.

Issue: #178

Description of changes:

Add support for Laravel 7

Closes #171. Closes #178.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The package method (called in boot) does a lot of file/directory checks when it is called. If you have an app that does a lot of things NOT related to AWS this will cause a problem. Would it be possible to set the service provider to be deferred?

This makes sure we're compatible with all versions of laravel 4 and laravel 5.

I've also updated to phpunit 4, and moved to psr-4 without modifying the directory structure.

Getting below error..

My queue region is "ap-south-1" AWS.SimpleQueueService.NonExistentQueue (client): The specified queue does not exist for this wsdl version.

Call never ends and never returns from getThingShadow, browser keeps quering..

$client = AWS::createClient('iotDataPlane');
$result = $client->getThingShadow([
     'thingName' => $thingName, // REQUIRED
    ]);

Also same with

$client->publish([ 'payload' => '{"test": "0"}', 'topic' => "test", 'qos' => 0]);

Topic gets published but it never leaves publish method.

What I am doing wrong ?

Description of changes: Adds support for Laravel 8

Changes:

• Bump supported version of Illuminate/support to ^8.0
• Bump the version of dotenv to include support for ^5.0
• Update docs to show support for Laravel 8

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Trying to just upload files. It feels like my key and secret arent working but i've double checked they are the right ones. Codes copied straight out of the readme.

Error:

Error retrieving credentials from the instance profile metadata server. 
When you are not running inside of Amazon EC2, you must provide your AWS
access key ID and secret access key in the "key" and "secret" options when 
creating a client or provide an instantiated
Aws\Common\Credentials\CredentialsInterface object.
([curl] 7: Failed to connect to 169.254.169.254: Host is down [url] 
http://169.254.169.254/latest/meta-data/iam/security-credentials/)

Function:

$s3 = AWS::get('s3');
$s3->putObject(array(
    'Bucket'        => '[bucketname]',
    'Key'           => '[key]',
    'SourceFile'    => '[file]'
)); 

The AwsServiceProvider currently doesn't work in a Lumen project, because the config_path helper function isn't available.

Would it be reasonable to change line 9 ($this->publishes...) to first check to see if config_helper has been defined?

From what I can tell $this->publishes... doesn't need to be run in a Lumen app anyway, and I can still configure Aws using my .env file.

I'd be happy to submit a PR, just wanted to see if this was the right approach.

Where is the best place (laravel code file) to drop in AWS dynamodb session handler in laravel 4, and any suggestions on changing configs to accomodate?

http://docs.aws.amazon.com/aws-sdk-php-2/guide/latest/feature-dynamodb-session-handler.html

Many thanks

Issue #, if available: readme link error

Description of changes: fix readme jump to link

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Describe the feature

Since v5.8 Laravel has provided example .env variables for configuring AWS settings, one of which is the AWS_DEFAULT_REGION key for configuring the default region (https://github.com/laravel/laravel/blob/5.8/.env.example). This package sets us-east-1 as the default region unless you define an alternative using the AWS_REGION key in your .env.

Suggest changing the environment key to use the same key that is already defined in the Laravel .env.example so that an effectively duplicate key does not need to be added. This also keeps it consistent with the other keys Laravel and the package share.

Use Case

No duplication of keys/values and keeps things consistent.

Proposed Solution

Update both config/aws_default.php and config/aws_publish.php to:

Replace

'region' => env('AWS_REGION', 'us-east-1'),

With

'region' => env('AWS_DEFAULT_REGION', 'us-east-1'),

Other Information

No response

Acknowledgements

• [ ] I may be able to implement this feature request
• [ ] This feature might incur a breaking change

SDK version used

3.7

Environment details (OS name and version, etc.)

Fedora 36

Describe the bug

I have a Lumen 8.0 app into which I'm trying to install this SDK.

1. I install via composer: composer require aws/aws-sdk-php-laravel
2. I add this line ($app->register(Aws\Laravel\AwsServiceProvider::class);) to bootstrap/app.php
3. I confirm I have the proper environment variables in place
4. I run php artisan vendor:publish --provider="Aws\Laravel\AwsServiceProvider"
5. I get this output: Unable to locate publishable resources. Publishing complete.

I tried manually importing that class:

use Aws\Laravel\AwsServiceProvider;
$app->register(AwsServiceProvider::class);
// and nothing

I tried running composer dumpautoload and then the vendor command and nothing.

I've found posts on Stack Overflow which suggest running the php artisan vendor:publish alone. That command output does not include anything related to AWS.

I even tried this suggestion found on the Lumen Vendor Publish package: https://github.com/laravelista/lumen-vendor-publish/issues/16#issuecomment-917424678

Can you offer any insights into why this might be failing? I suspect I could simply copy vendor/aws/aws-sdk-php-laravel/config/aws_publish.php into my config/ directory as aws.php but given you have specific instructions for Lumen I thought I'd ask here first.

Expected Behavior

I expected the file config/aws.php to be created as per the instructions in the readme.

Current Behavior

When I run this command:

$ php artisan vendor:publish  --provider="Aws\Laravel\AwsServiceProvider"

I get the following output:

Unable to locate publishable resources.
Publishing complete.

Reproduction Steps

1. I install via composer: composer require aws/aws-sdk-php-laravel
2. I add this line ($app->register(Aws\Laravel\AwsServiceProvider::class);) to bootstrap/app.php
3. I confirm I have the proper environment variables in place
4. I run php artisan vendor:publish --provider="Aws\Laravel\AwsServiceProvider"
5. I get this output: Unable to locate publishable resources. Publishing complete.

Possible Solution

It appears that the publish command can't find the package, but it's clearly there when viewing the vendor folder.

Additional Information/Context

No response

SDK version used

3.7

Environment details (OS name and version, etc.)

Mac OS 10.15.7 (19H1615)

Description of changes:

Let's ignore these files and folder while installing this package via composer.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Confirm by changing [ ] to [x] below:

• [x] I've checked AWS Forums and StackOverflow for answers
• [x] I've gone though Developer Guide and API reference

Version of AWS SDK for PHP? Example: v3.133.6

• get SDK version by printing the output of Aws\Sdk::VERSION in your code
• if the SDK was installed via composer you can see the version installed with composer show -i

Version of AWS Service Provider for Laravel? 3.6

Version of Laravel (php artisan --version)? 8.15.0

Version of PHP (php -v)? 7.4.1

Describe the question After running the command: php artisan config:cache for some reason I always got this error:

Error retrieving credentials from the instance profile metadata service

If I'll use the following command: php artisan config:clear it's work fine. Now, to work with the socket server I need those cached config files. Basically, as I understand if I will cache the configuration file, the SDK cannot see the connection credentials. Basically, the issue is not only with only one AWS service it's with all of them (SNS, SES, S3, SQS, etc).

Description of changes: Since Laravel 5.7 where they added the default environment variables for AWS to the .env.example the region variable has been called AWS_DEFAULT_REGION, however this package by default looks for AWS_REGION and then falls back to us-east-1.

This PR adjusts the confirm file to first look for AWS_REGION else AWS_DEFAULT_REGION else us-east-1.

This is a non-breaking change.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.