stanleyho , That is why in our department we are using LRE iso LRP. Auto deployment of LGs in AWS, no external access needed, only inside the VPC. SSO access to LRE server. The Controllers live only inside the VPC as well. For admin RDP access we use AWS SSM access (can be tight to SSO as well).

Unfortunately our department is not using LRE.
We only use AWS resources to for internet facing applications and for high user concurrency load.

Most of our target applications are intranet based. As it is hosted within private environment and clients' security concerns, we can't use resources from public internet as test machines.

I believe all vendors have their own budgets and use cases to implement LRE.

LRE has the 'concept' of LG's over firewall. The on-prem LGs reach out to a LRE-listener near LRE to conact. This is how we implement on-prem (or cross AWS account) testing. We use strict IP whitelisting on the LRE-listener from the on-prem locations (and one can secure further).

Aware of the features of LRE.

Unfortunately, we are not testing any in-house application within our organisation.

We are providing testing services to our clients. Thus we don't have the luxuries of implementing the required resources within clients privately hosted environments. Furthermore, our clients engages our testing services on ad-hoc basis.

As such, my superiors do not see a strong use case for LRE.

Yes agreed, LRE in a consultancy organization on an adhoc-basis is less useful indeed. I do not need to tell you how beneficial performance regression testing is. But for the end-users it is a grow path to maturity of their product stack.

Yes agreed, LRE in a consultancy organization on an adhoc-basis is less useful indeed. I do not need to tell you how beneficial performance regression testing is. But for the end-users it is a grow path to maturity of their product stack.