open_basedir is not within the allowed path(s)

[ljay88]

Warning: is_readable(): open_basedir restriction in effect. File(/home/www/.aws/config) is not within the allowed path(s): (/www/wwwroot/test/:/tmp/) in /www/wwwroot/test/vendor/aws/aws-sdk-php/src/Retry/ConfigurationProvider.php on line 158

Warning: is_readable(): open_basedir restriction in effect. File(/home/www/.aws/config) is not within the allowed path(s): (/www/wwwroot/test/:/tmp/) in /www/wwwroot/test/vendor/aws/aws-sdk-php/src/S3/UseArnRegion/ConfigurationProvider.php on line 134

Adding the following configuration does not work

'csm' =>false,

[SamRemis]

Hi @ljay88,

I could use a little more context here. I see the lines that you're referencing, but what code of yours is calling the lines. Can you provide me with some code that I can use to reproduce the issue so that I can confirm it's fixed once I've patched it?

[ljay88]

date_default_timezone_set('PRC');
require DIR . '/vendor/autoload.php';

$s3 = new Aws\S3\S3Client([
'version' => 'latest',
'region' => 'us-east-1',
'csm' =>false,
'endpoint' => 'http://192.168.3.10:9000',
'use_path_style_endpoint' => true,
'credentials' => [
'key' => [redacted],
'secret' => [redacted]
]
]);

$command = $s3->getCommand('GetObject', [
'Bucket' => 'test',
'Key' => 'test.jpg'
]);

[SamRemis]

try setting 'use_aws_shared_config_files' => false in the client, it should skip checking those config files you don't have access to.

$s3 = new Aws\S3\S3Client([
'version' => 'latest',
'region' => 'us-east-1',
'csm' =>false,
'endpoint' => 'http://192.168.3.10:9000',
'use_path_style_endpoint' => true,
'use_aws_shared_config_files' => false,
'credentials' => [
'key' => [redacted],
'secret' => [redacted]
]
]);

[ljay88]

Thank you very much, I will try

[SamRemis]

@ljay88 Thank you :) please let us know if this doesn't work, or if it does close the issue (or let me know so that I can)

[ljay88]

Thank you very much, it works normally

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[JorisDebonnet]

@SamRemis, I had this problem too, and found this page when searching. I would like to request reopening this issue.

Reasoning: it's not considered "nice" to require users to circumvent an issue by adding extra configuration. A "nicer" solution would be if this package just had a more graceful handling of this situation.

I believe the fix is straightforward: just wrap these particular is_readable calls in try/catch (and make it return 'false' in the catch). After all, everything still works perfectly fine if is_readable does not return true, so there isn't really a reason to 'bother' the developer about it :D

[SamRemis]

@JorisDebonnet That's true; I have to think about if this is potentially breaking change for anyone, but off the top of my head, I don't see a reason that a user would be relying on this particular failure.

I will re-open this and add the feature request label to it, and chat with the team to make sure that this change isn't potentially going to break anything for a customer.