Using the Cloud URL instead of ID to connect .NET client app to Elastic Cloud

Hi, we had an issue after applying Azure private link traffic filter to our deployment, authenticating with Cloud Id no longer works.

We are considering to use URL instead but we see it is not recommended:

When connecting to Elastic Cloud with the .NET Elasticsearch client you should always use the Cloud ID.
We recommend using a Cloud ID whenever possible because your client will be automatically configured for optimal use with Elastic Cloud, including HTTPS and HTTP compression.

Can someone provide more details on pros and cons of using it?


1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.