ISSUE SUMMARY:

I enabled the S3 feature for our site. When the cron runs, the files are transferred to the S3 bucket, but after that, on the front-end there are broken images. I noticed that the file s3_lib.php hard coded the amazon url as "s3.amazon.com". However, the Amazon S3 endpoint for my bucket is akjn.s3-website-ap-southeast-1.amazonaws.com. We tried changing that in the file s3_lib.php as well, but still the images are broken in the frontend.

We are currently testing JS 4 with the Socialize template on our development server - ajdev.in. The production site is akankshajunction.com which is still running an older version.

Request your help on the development server, please. Have provided the credentials in the private area.

Thank you
Best regards

Praveen



STEPS TO REPLICATE:
1
2
3
4
5
RESULT
EXPECTED RESULT
BROWSER

HI, Praveen.

I assign developer to this thread.

Hi Praveen,

do already setup your amazon S3 correctly? Because when I execute the cron job. there is no any files transferred.
please revert back any file changes at jomsocial core. and amazon URL by default always <bucket>.s3.amazonaws.com.

please follow this doc carefully:
documentation.jomsocial.com/wiki/Setting_up_Amazon_S3

Regards

Hi Albertus,

We managed to get this working. There was a typo in the S3 URL we entered in the Jomsocial backend configuration. With the correct URL, it works like a charm. Also, the cron did not transfer any pictures because there were none to transfer, as this is a development site. We had to make changes to the original S3 files because the S3 URL was hard-coded in some places as "s3.amazonaws.com". However, if you setup a bucket in a different AWS region, the bucket URL looks something like "akjn.s3-website-ap-southeast-1.amazonaws.com".

Plus, while setting up the bucket, we need to enable static site hosting and give the following AWS policy for the bucket:

{
"Version":"2012-10-17",
"Statement":[{
"Sid":"PublicReadGetObject",
"Effect":"Allow",
"Principal": "*",
"Action":["s3:GetObject"],
"Resource":["arn:aws:s3:::example-bucket/*"
]
}
]
}

This is also given on the Amazon site at docs.aws.amazon.com/AmazonS3/latest/dev/...PermissionsReqd.html

You may want to include this in your documentation, after checking it out.
After we made these changes, the S3 feature works like a charm.

Thank you
Best regards

Praveen