Hi Chris,

No, Laserfiche Cloud does not support customers establishing a private Direct Connect circuit with the service. Direct Connect to SaaS applications is not, as far as I'm aware, a thing. AWS has an example PrivateLink + Direct Connect model for private SaaS connectivity, though that's not something Laserfiche Cloud is architecturally set up for.

If a customer has Direct Connect to their own VPC in the same AWS region as Laserfiche Cloud and sends their end user/LF Remote Agent/etc. traffic through it, they will likely see some indirect performance benefits. Laserfiche Cloud-bound traffic will exit a public network interface in the customer VPC and go right back into one the Laserfiche Cloud public AWS interfaces. This would keep relevant traffic mostly off of the public internet.

Edit 9/2/2022:

@████████

Direct Connect Gateways have two different types of endpoint interfaces - public and private. Public Gateway endpoints are to an AWS region at large and provide direct connectivity to AWS services public API surfaces in that region - e.g., anything served directly through S3. Private Gateway endpoints have to terminate in a specific VPC to access resources in that VPC (e.g., Laserfiche Cloud servers in the Laserfiche Cloud VPC).

A customer with Direct Connect and a Public gateway interface will get a few Laserfiche Cloud resources served to them a few milliseconds faster - mostly static assets hosted in S3 that your browser caches after the first load anyway. Everything else would take the public route.