I have a test server running Dataverse 5.14, talking to Amazon S3. I can, using the credentials specified in jvm-options and in ~payara/.aws/credentials, upload and download test files using the AWS CLI. I have disabled upload-direct and download-direct in domain.xml. I have quadruple-checked my S3-related jvm-options. No matter what I do, Amazon complains, returning a 403 Forbidden when Dataverse attempts to retrieve the bucket ACL, then another 403 Forbidden when Dataverse attempts to upload a file. I am allowing GetBucketACL in the policy attached to the IAM role. Any ideas or suggestions would be most welcome. Thank you, Don
Which version? I remember Jim fixed some auth ordering in some release, that might cause trouble. Don't remember the deets though :melting_face:
Maybe we can do a quick screen share sometime to quadruple check the settings. :grinning:
Sry it's late here. 5.14... :sweat_smile:
Yeah the fix was done in 6.1, see #10003 / #10004
Oliver Bertuch said:
I was looking at the issue/PR, but we arenβt using RBAC, just keys. The ordering issue was reported in 5.14 when RBAC support came back on the scene, and I have 5.12.1 and 5.13 servers which seem to behave just fine.
@Philip Durbin I would love a screen share, though at some point today I have a meeting with Jamie to talk about LetsEncrypt within Dataverse-Ansible, and also her 403 Forbiddens. Note that she was running 5.14 with no S3 woes, so I'm curious how her S3 creds are defined.
Well, she's on the west coast. If you're available now, I'm around. :grinning:
@Philip Durbin I have an 0945 with Sonia, then I may pester you?
sure!
Found it. A forgotten experiment from 3 years ago was lurking in our AWS configuration. Good to know about the RBAC preference bug between 5.14-6.1, though.
Don Sizemore has marked this topic as resolved.
Last updated: Oct 30 2025 at 06:21 UTC