Streaming worked three weeks ago, before I started this ticket. Something changed between WPEngine, s2Member and AMazon AWS–and it also affects this bare bones site. I now see that the theme and plugins are not part of the problem.
Thanks for your tests without the other plugins and theme.
Yes, something seems to have changed with one of those three, and I’m guessing it’s WP Engine. I just tested the mod-rewrite format with a file in my own test installation with Amazon S3+CF integration, and I could download the files just fine using the same URL format you’re having trouble with:
http://www.ourdomain.com/wp-content/plugins/s2member-files/s2member-file-remote/s2member-file-inline/filename.mp3
I just tested again and there’s definitely something wrong with your mod-rewrite.
Now, I don’t know if it’s a requisite to use that format for your streaming, maybe the querystring one is good enough for your use? But it’d still be good to have your hosting solve the mod-rewrite issue.
If you try /wp-content/plugins/s2member-files/filename.mp3 (a file you have in your S3 bucket), you’ll see a 404 that mentions WP Engine in the footer, but if you try /wp-content/plugins/lkjdfsjlkdlfs.html you’ll get a different 404 without the WP Engine mention. I find this odd, but is what made me thing the problem may be with their configuration.