S3 integration stopped working properly

Hmm, when I look into my test buckets, it always shows me the links as <region>.amazonaws.com/<bucket>/<file>.

Where did you read that this would be wrong?

All I know is that either one should work. If you want to use the bucket as part of the DNS, then it must be DNS compatible, however if you use it in the path part (like it's now), then you can name the bucket like you want.
This means the current behaviour is less likely to cause problems if the bucket name has special or uppercase characters.

Maybe in your case it's the issue David pointed out initially. If your not using a standard US bucket, then the link SermonSpeaker generates is wrong as it misses the region.
Try the suggested fix and resave the sermons.

Amazon pointed met to the bucket.amazon.etcetera order.
But your latest update (4.4.10) has fixed the issue.
I can upload to s3-eu-west-1.amazonaws.com and use the sermons.
Thanks for your hard work on this component! You bless a lot of people by it!

Thanks for the feedback. I'm glad the issue is fixed.