Hello Robin,
thank you.
The object-stat did not show anything suspicious.
And the logs do show
s3:get_obj decode_policy Read AccessControlPolicyxmlns="http://s3.amazonaws.com/doc/2006-03-01/;>XY
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
On Thu, Mar 21, 2024 at 11:20:44AM +0100, Malte Stroem wrote:
> Hello Robin,
>
> thanks a lot.
>
> Yes, I set debug to debug_rgw=20 & debug_ms=1.
>
> It's that 403 I always get.
>
> There is no versioning enabled.
>
> There is a lifecycle policy for removing the files after one day.
Did the
Hello Robin,
thanks a lot.
Yes, I set debug to debug_rgw=20 & debug_ms=1.
It's that 403 I always get.
There is no versioning enabled.
There is a lifecycle policy for removing the files after one day.
That's all I can find.
Do you have any more ideas?
Best,
Malte
On 19.03.24 17:23, Robin
On Tue, Mar 19, 2024 at 01:19:34PM +0100, Malte Stroem wrote:
> I checked the policies, lifecycle and versioning.
>
> Nothing. The user has FULL_CONTROL. Same settings for the user's other
> buckets he can still write to.
>
> Wenn setting debugging to higher numbers all I can see is something
