The other solutions you have where you authenticate the path as such, which should ideally be used for more sensitive assets:
- Proxy asset requests through application server, let it authenticate the user access. You can even generate short lived S3 urls this way, and your objects don't have to be public.
- Proxy asset requests through a reverse proxy like Nginx, authenticate there, you have a lot of options here like using something like JWT to authenticate the resource access.
- Proxy asset requests through your reverse proxy CDN like Cloudflare, authenticate there, like in case of Cloudflare JWT is supported.
The problem is that it means the requests can't really be cached, so for static assets it's not ideal. S3 supports etags though but I've never touched that so I don't know how well it all works; I personally don't use signed URLs for stuff I want cacheable.
4) I would say is the best and the safest solution at really low cost. Followed by 1) at price/value ratio.
Protecting from MITM is a separate (important) concern for that approach to be valid though, and it's not 100%.
If you use an integrated cloud+cdn solution, the problem is largely solved for you, assuming you pick up the best practices and run with them
Another problem is if the random image id is leaked.