Robin Moffatt03/01/2023, 4:01 PM
Guy Hardonag03/01/2023, 4:09 PM
Replacing the first
should do the job
Robin Moffatt03/01/2023, 4:20 PM
Guy Hardonag03/01/2023, 4:44 PM
Robin Moffatt03/01/2023, 5:48 PM
I can still browse and see the folder contents, but if I click on the object I get an error. Is the error showing the permissions are working? I'd have expected not to be able to browse the contents either
Iw: Iw at ot (<https://rmoff-test.us-east-2.lakefscloud.io/assets/index-6dd372f1.js:67:10488>) at async VG.head (<https://rmoff-test.us-east-2.lakefscloud.io/assets/index-6dd372f1.js:67:21061>) at async <https://rmoff-test.us-east-2.lakefscloud.io/assets/index-6dd372f1.js:67:29262>
Guy Hardonag03/01/2023, 5:50 PM
Robin Moffatt03/01/2023, 6:07 PM
Guy Hardonag03/01/2023, 6:09 PM
and that error I’m seeing there is the one saying “access forbidden”?It is, but I agree the error isn’t clear would you like to open an issue for that, or would you like me to?
Ariel Shaqed (Scolnicov)03/01/2023, 7:28 PM
To use this action in an AWS Identity and Access Management (IAM) policy, you must have permissions to perform the s3:ListBucket action.
It's an object store thing: there really are no directories!
Robin Moffatt03/02/2023, 2:53 PM