Summary

The FaaS detection logic added in DRIVERS-2209 can mistakenly identify EKS as AWS Lambda.

For example in HELP-54555, this connection handshake metadata was sent even though the app was not using Lambda or using 256MB memory:

"env": {"name": "aws.lambda", "region": "us-east-1", "memory_mb": 256}

Instead the app was hosted in EKS with 2 GB memory. CPU memory config from k8s container is as follows:

resources:
   requests:
     memory: 2Gi
     cpu: 1000m
   limits:
      memory: 5Gi
      cpu: 5000m

Motivation

How does this affect the end user?

This behavior is confusing for users, support engineers, and results in potentially unwanted changes in MongoClient behavior (eg serverMonitoringMode).

How likely is it that this problem or use case will occur?

Unknown. Need to investigate EKS to reproduce.

Acceptance Criteria

Investigate EKS to reproduce and fix false positives. Audit GCP, Azure, and other platform detection logic to see if those can be improved too.