Cannot get media sources to work with Amazon S3

I have not been able to get an Amazon S3 bucket setup as a media source, everything looks right in the setup screen, but nothing appears in the file browser when I save the source ... no errors, nothing I can't even tell if it's trying to connect...

Modx error log:

[2012-02-24 19:20:23] (ERROR @ /var/www/vhosts/domain.com/httpdocs/core/model/aws/sdk.class.php : 27) PHP warning: file_exists() [<a href='function.file-exists'>function.file-exists</a>]: open_basedir restriction in effect. File(/root/.aws/sdk/config.inc.php) is not within the allowed path(s): (/var/www/vhosts/domian.com/httpdocs:/tmp)


[2012-02-24 19:20:23] (ERROR @ /var/www/vhosts/domain.com/httpdocs/core/model/aws/lib/requestcore/requestcore.class.php : 817) PHP warning: set_time_limit() has been disabled for security reasons

File(/root/.aws/sdk/config.inc.php) is not within the allowed path(s): darn straight it isn't!
could set_time_limit() being disabled be causing this to not work?

ideas?

-sean

Still fighting with this... got the correct credentials, now looking at the instance name....

""

What is that supposed to be?? the account ID, the login user name the account number? I can't find anything in the Amazon console that refers to an "instance name"

no errors, nothing...

getting frustrated.

Sort of solved, there are 'gotchas' though.....

I never did find the 'account/instance name' in the amazon console, luckily I managed to guess it, I dunno where it comes from because it isn't the user name, id or account id... anyway I was having trouble because my instance name and my bucket seem to be accessible a couple of different ways:

I can access the bucket via:
instance name = http://my-guessed-account.s3.amazonaws.com/
bucket name = some-bucket-name

but when I try to associate that to a file type TV it gives me the wrong link to the file in the bucket, I get :
http://my-guessed-account.s3.amazonaws.com/some-file.txt
when the actual url to the file is:
http://some-bucket-name.s3.amazonaws.com/some-file.txt


Finally I set it up like this:
instance name = http://some-bucket-name.s3.amazonaws.com/
bucket name = some-bucket-name

and it seems to be behaving, though without the bucket name, it fails again. To my mind, that should not work set up like that...

-sean

Hi,
did you change anything in the Bucket settings (ACL to Everyone etc.)? I am trying to get it working and since I have no idea of the account name I am a bit lost.
Do you have a hint where to find it?

no I never did find an account name,. but all I have in the instance is the full url to the amazon bucket & the bucket name... [well the keys as well]

:)

Well - I am trying to get it working as a media source and tried almost everything.
url: http://bucket-name.s3.amazonaws.com/
bucket: bucket-name
+key and secret_key

What amazes (haha) me is that if I use the credentials in a client or firefox extension - it works. But as a media source in MODX I cant get a file-listing at all.

anything in the modx error log? seems to me that it did that at one point... not sure.

do check your amazon permissions [though it shouldn't matter if you are just trying to connect.] ..

hmmm also maybe the cache? I seem to remember something about that....

If anyone else stumbles across this, then it is also useful to mention that your bucket should not have periods in it e.g. assets.mydomain.com (which is handy for CNAMEs) as it causes issues with the SSL certificate (see https://forums.aws.amazon.com/thread.jspa?threadID=69108).

Make sure to clear your cache too

For all those who arrive here by search:

wiseguydigital is correct: your bucket name CANNOT have any periods in it. This detail kept me running around in digital circles for an inordinate amount of time.

After a ton of searching I found a solution that worked for me for BUCKET NAMES WITH PERIODS IN THEM!

edit /core/model/aws/services/s3.class.php and update to be the following.

/**
* The DNS vs. Path-style setting.
*/
#public $path_style = false;
public $path_style = true;


BAM! Everything works...

Should really make it easy to change this within modx's system settings....