Hello, @chris.brenden
Thanks for reporting the issue.
If you carefully followed the documentation for the plugin and this issue appeared, the reason is the wrong JSON settings. Please copy and paste the following codes into their respective blocks:
Bucket policy
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "AddPerm",
"Effect": "Allow",
"Principal": "*",
"Action": "s3:GetObject",
"Resource": "YOUR_ARN_HERE/*",
"Condition": {
"StringLike": {
"aws:Referer": "YOUR_DOMAIN_HERE/*"
}
}
},
{
"Sid": "AddPerm2",
"Effect": "Allow",
"Principal": "*",
"Action": "*",
"Resource": "YOUR_ARN_HERE/*"
}
]
}
ACL
CORS
[
{
"AllowedHeaders": [
"*"
],
"AllowedMethods": [
"GET",
"PUT",
"DELETE",
"POST"
],
"AllowedOrigins": [
"YOUR_DOMAIN_HERE"
],
"ExposeHeaders": [
"ETag"
],
"MaxAgeSeconds": 30000
}
]
Save the setups, then give it a try again, please.
Best regards,