Lambda Edge in Origin request does not trigger at edge location but at regional edge location even when behaviour caching policy is CachingDisabled

I am not sure if this is intended, is a default behaviour, has a configuration or possibly a hack. I have some requests originating from within the Saudia Arabia and UAE region, and a frontend and backend that sit under the same domain through cloud front and i handle the routing through the path pattern where the website sits on a s3 behind one pattern and the other path pattern sends requests to the backend. Before sending the request to backend, however, an Edge Lambda is invoked as a reverse proxy and path rewriter. However, when i check Function Metrics from under Cloud Front Telemetry Monitoring for the Edge Lambda, i see that nearly all of the invocations lie in Frankfurt or Ireland. Based on the map here https://aws.amazon.com/cloudfront/features/?whats-new-cloudfront.sort-by=item.additionalFields.postDateTime&whats-new-cloudfront.sort-order=desc i would expect the invocations to be within the Saudia/UAE region and but instead i see the invocations in the Frankfurt region from where it is then sent to the backend which is at Mumbai leading to a longer trip. On searching up a bit I found that there is a concept of Regional Edge Locations as well which act as the second layer of cache after the edge location and all my invocations lie there. To somehow get the Lambdas to trigger at the edge locations instead of regional i tried setting the Cache Policy to CacheDisabled, legacy cache settings to All Headers and some hacks like setting the max age and expire headers in the api requests but the invocations consistently lie at their previous locations.