How to bypass service blocking (forward-proxy)?

Question

proxy

Colleagues, who bypasses the blocking of AWS and other services for their clients?
There are, for example, lessons (lessons.someblockedservice.com) on someone else's learning service in AWS and I don't care about my clients who use these lessons, but quickly move somewhere from this service to another that (yet) does not blocked is not an option. Therefore, I raised my forward-proxy to nginx in a neutral DC and proxy requests from my domain with lessons (lessons.myownservice.com) to the same external service.
However, not all requests and URLs in responses can be replaced with your own domain. There is another idea to try the same on Squid.
But maybe there are already ready-made services for such purposes? In fact, we need a little-known analogue of CloudFlare outside the Russian Federation, which, most likely, will not be banned.
The most difficult thing with such proxying is to catch all the used URLs, of which a couple of dozen and some of them are dynamic, i.e. a simple replacement of someblockedservice.com -> myownservice.com is not enough.

Answer 1

Haproxy