We could set up a let’s encrypt for each server that is created from capella ?
You can use the Feedback link on Capella to make the suggestion.
There are 42 jira tickets that mention letsencrypt, but only two are public.
Issue navigator - Couchbase Cloud (not public) discusses using letsencrypt in capella
Issue navigator - Couchbase Cloud
The default certificate is built-in to the SDKs. Using Couchbase without the SDKs (i.e. http) is not trivial and not a good user experience.
I just submitted the feedback, but not sure how long it’ll take to implement
I think it shouldn’t be any different from native vs http, it should work regardless, because right now it looks like you cannot run couchbase on edge environments(cloudflare workers via HTTPS), it must have a full nodejs environment to work.
Meaning couchbase isn’t 100% serverless.
You can provide whatever certificate you want to the server. I don’t believe the provided, self-signed certificate was ever intended for production use.
I meant capella here,
i agree, it looks like i’ll have to run a self hosted cluster then provide the certificates (not sure how to add them in capella) or mask it to normal HTTPS/TLS ports then cover it with let’s encrypt
Right - only on-premise has a mechanism for uploading certificates. Capella does not.
App Services have certificates from a well-known CA. Not sure if that helps.
Yes, i looked into it, Looks super nice, to my understanding it works best for end-user apps, where a client app accesses the data directly but not for server environments (where running sql queries, indexing, cluster configs, doc locks, e.t.c …).
The ticket you opened via Feedback is AV-89567 - it’s not public, but whenever you want to bring this up with anyone at Couchbase, that’s the reference to use.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.