imgproxy and private network
erkage
HOBBYOP

2 years ago

Hey,

Hope you're well.

I just want to make sure that I thinking correctly when I try to achieve the following:

And I'd like to change that external url for an internal one - for optimisation so imgproxy would just fetch the image internally which faster and doesn't count as egress - so I assume that it would be:
https://my-imageproxy.up.railway.app/_/plain/https://backend.railway.internal//uploads/myimage.png
but it doesn't seems to work right now.

So I'd like to get a feedback that Private addresses should work like this and I should just deep dive into some configs for imgproxy (which I have already done but without luck).

Thanks in advance,
Gabor

3 Replies

ray-chen
EMPLOYEE

2 years ago

That's do-able if your proxy service calls the internal service over private networking to fetch the image and serve it to the public, however if I'm understanding this correctly:

for optimisation so imgproxy would just fetch the image internally which faster and doesn't count as egress

imgproxy would incur the egress cost of serving the images to public, so this sounds like it's adding a layer of abstraction for zero gains?

erkage
HOBBYOP

2 years ago

Thanks for your reply Ray.

For serving to public, yes, but now when it's fetching the image - if I'm thinking correctly - it reaches out from Railway's network (as I'm using the public address) so I'd like to save on this using the private network.

And I might know what was unclear in my description: imgproxy (https://github.com/imgproxy/imgproxy) is not just a proxy service it's a image processing tool, so it can for example resize images with adding "/size:500/" to the url and for that it first fetch the image from the given url.

ray-chen
EMPLOYEE

2 years ago

You'd want to ensure that your Medusa service binds to :: (IPv6 equivalent of 0.0.0.0) so that it's reachable over private networking.

For serving to public, yes, but now when it's fetching the image - if I'm thinking correctly - it reaches out from Railway's network (as I'm using the public address) so I'd like to save on this using the private network.

So the data flow looks like:

Internet -->[public networking]--> Imgproxy -->[private networking]--> Your Service

When a user requests an image, you fetch it over the private network, and serve it to them, right? The last step would still incur egress cost as it's traffic that's going out (no matter where the contents of the traffic originates from).

With the resizing/optimizations that imgproxy offers, you might be able to save some amount on egress cost, however egress is still a thing if traffic is going out to the internet/end user.

Unless you're "double-fetching" the media right now?

Loading...