It looks like the lambda does not have access to the cluster. Please make sure you’ve exposed all relevant ports (Couchbase Server Ports | Couchbase Docs) and can contact them externally.
Those are only the non-ssl ports. For ssl, the ssl ports also need to be accessible.
You can use curl to check that the ports are accessible - timeout means they are not exposed, anything else - include errors is exposed (curl will give errors when a non-http/s port is accessed).
Presumably “connection string” is not your actual connection string
No, the SSL ports shouldn’t be used if you’re not using SSL.
But this is still likely to be a basic connectivity/ports issue. You’ve shown the AWS lambda inbound rules, but where is the cluster hosted - what about the inbound & outbound rules configured there? Can you connect to the cluster from your laptop? sdk-doctor (GitHub - couchbaselabs/sdk-doctor: Application-server-side cluster connection diagnostics.) can be useful for identifying connectivity problems.
Cluster hosted on EC2 under the same account and region as lambda which uses Couchbase. Cluster has exactly the same security group as lambda (you can check the screenshot with lambda inbound rules above)
Each 6 - 10 request to Lambda occurred retries with
But they eventually succeed? If they fail can you show the stack trace?
The messages - especially the DEBUG message that says “ignored on purpose” is a not a fatal error. To get the configuration, couchbase will try the management service if it fails to get the config from the kv service. And it will also retry. The operation may timeout, but won’t fail when couchbase temporarily does not have a connection.
Can you show the connection string you are using? Can you show the SDK Doctor command and all the output from it?
I’m using Java 11 with JDK version 3.4.1
Without any particular change in mind, the newer versions tend to work better. Could you try 3.4.6?