Security Credential issue.

[allanhortle]

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]'
)); 

[jeremeamia]

The error you are receiving happens when credentials have not been provided. The SDK will attempt to look for instance profile credentials in this case (which are only available on a properly configured EC2 instance). How are you providing your AWS credentials to the SDK?

[allanhortle]

They are just sitting in the array in config.php

[ArthurGuy]

I am having the same problem.
The facade is looking for a config files called aws.php in the main config directory, it seems to be ignoring the package specific files.

[jeremeamia]

@ArthurGuy and @allanhortle, are both of you using the latest version (1.1.0) of the service provider? If so, do you have any ideas why this might not be working correctly? When I released 1.1.0 a couple of months ago, everything seemed to be working fine.

[adamgoose]

@jeremeamia I'm getting the same issue. Turns out the service provider isn't getting proper access to the config file. My guess is that it has something to do with the custom namespace you're using. I'm researching, and will submit a PR when I have it figured out.

[jeremeamia]

Thanks for taking a look @adamgoose. Is something incorrect this line?

[adamgoose]

The issue is this: the boot command is only called right before a request is routed. Meanwhile, the register method is called immediately when the service provider is registered. Thus, you are trying to register into the IoC container BEFORE you run $this->package('aws/aws-sdk-php-laravel', 'aws'), which defines the namespace. This means that your register() method does not have access to the properly namespaced config. The solution: move $this->app['aws'] definition into the boot method.

[adamgoose]

I'll submit a PR to do this for you.

[adamgoose]

Strange... Deleting the vendor directory and running composer update fixed my issue... Not sure PR #24 is required.

[jeremeamia]

OK. That kinda makes sense. I thought I had this working in version 1.1.0. I talked to Taylor on IRC last night, and it was working for him as well. Is it possible that Composer was giving you a cached, older version of the module or something?

[jeremeamia]

I'm going to go ahead and close this issue for now. I appreciate everyone's help looking into this.