@patrick
https://community.wappler.io/t/s3-custom-provider-add-region-field-and-make-code-a-bit-more-custom-provider-friendly/24422/24?u=philiph
This is not fixed, I have got the same issue in Wappler 4.8.2.
My endpoint pattern is “my-name.s3.fr-par.scw.cloud” and throws the same error as the one discussed in the topic I mentioned.
Waiting for an update containing the fix, is there any workaround?