have you tried with CORS configured? does the console or browser dev tools provide more or different errors? you might need to delete the S3 bucket name field since the base url specifies the bucket name... the resulting request might be trying to access a nested bucket or something.
if you put the normal non-accelerated url in the Base URL field does it work? if not, I'd guess permissions are actually the issue here.
i guess a workaround might be to use a JS Query and manually use fetch() or whatever instead of the S3 resource when you want to use the accelerated endpoint
just a couple things i noted from the aws docs:
- After Transfer Acceleration is enabled, it can take up to 20 minutes for you to realize the performance benefit. However, the accelerate endpoint is available as soon as you enable Transfer Acceleration.
I just notcied this though:
Transfer Acceleration is only supported on virtual-hosted style requests. For more information about virtual-hosted style requests
which might mean enabling force S3 URLs to use path style could be causing problems, since the api expects virtual-hosted style only trying to read a path style url as such would lead you to an invalid endpoint/bucket.