I’m really confused by your email reply…
My issue is with the S3 add-on, not Web Hooks add-on. Was the reply meant for someone else?
I tried installing the latest Web Hooks add-on, in case the reply was meant for me, to fix the S3 issue. However, there was seemingly no change with the S3 problem.
The back end works fine, but the front end Download fails if I set S3 bucket permissions to the same user the wpdm admin is using. The only way the front-end works is if I change the bucket policy to let “*” (anyone in the world — not authenticated users) access the bucket.
Forum user motografik mentioned in this thread that he reverted to an older version of the S3 add-on and it fixed the issue (assuming he was indeed addressing the same issue I and the OP are having.) Do you know if this is true? (If so, and it’s stable, how might I get it, and what changes in the newer version would be lost?)
I really would like to get this working asap. Any help is appreciated.
Thank you!
Here is an example of my bucket permissions (wpdm Downlaods fail, but user credentials on back-end are same):
{
“Id”: “Policy1426198988997”,
“Statement”: [
{
“Sid”: “Stmt1426198332740”,
“Action”: “s3:*”,
“Effect”: “Allow”,
“Resource”: “arn:aws:s3:::BUCKET-NAME/*”,
“Principal”: {
“AWS”: [
“arn:aws:iam::ACCOUNT_NUMBER:user/USER_NAME”
]
}
}
]
}
Modifying the Principal only, to “*” allows WPDM Downloads to work, but my bucket is open to the world (unacceptable):
{
“Id”: “Policy1426198988997”,
“Statement”: [
{
“Sid”: “Stmt1426198332740”,
“Action”: “s3:*”,
“Effect”: “Allow”,
“Resource”: “arn:aws:s3:::BUCKET-NAME/*”,
“Principal”: “*”
}
]
}
Additional Note:
“Access Permissions” set for Authenticated Users seem to have no affect
