S3 redirect does not work if image style path contains a prefix

/drimage/2720/1530/674/-/ looks like it is a control system of some kind for the drimage module to function correctly especially since the info page says It is meant to take the pain away from configuring and maintaining responsive image styles by simply not needing any configuration..

If you bypass this I suspect you will not actually have a working deployment with that module, content may be delivered based off the drimage_1024_ image style without customization.

Nginx could likely be configured to rewrite to s3fs's path, however if at that point if the module is not functioning there would be no need to keep it installed, which would remove the need to rewrite the URL at Nginx.

This isn't just a prefix, this is the drimage module provide its own independent image style controller to modify the response. S3fs needs to provide a controller controller for the s3fs provided schemes provide the redirect.

This unfortunately is an area where Drupal Core is not well equipped to handle multiple providers at the moment. Long term the solution is likely ✨ Split ImageStyle into the config entity and a separate event-based image processing service Needs work . Short term you may need to investigate using Core built in responsive image styles. DrImage might be able to fix this in an agnostica manner by checking if the image is on a remote stream wrapper, and redirecting to the target URL.

For context this is a similar to the following issues that involve competing controllers.
✨ Support webp module Closed: won't fix
✨ Support webp image style generation via imageoptimize_webp module Closed: won't fix