Unfortunately this seems to be a more complicated issue and we haven't been able to identify the root cause yet. We'll probably have to raise this with our S3 provider, as I couldn't find any public resources where they'd have announced any changes on their end.
fyi @Agent_Karyo@piefed.world (not sure if you're subscribed to all comments on this)