Elastic Cloud Private Link connectivity for clients with CloudID

Elastic Stack Elasticsearch
2

Hi @kiwibel

Welcome to the community and thank you for using Elastic Cloud.

Yes the cloud.id decodes to the normal public URL.

Once the VPC PrivateLink us set up unless you specifically also allow the public IP ingress it will no longer be available.

The Node / JavaScript client (assuming it is in your AWS VPC) can simply connect with basic authentication using the new URL.

const { Client } = require('@elastic/elasticsearch')
const client = new Client({
  node: 'https://XXX.vpce.ap-southeast-2.aws.elastic-cloud.com:9243',
  auth: {
    username: 'elastic',
    password: 'changeme'
  }
})

OR you can also add back / allow Public IPs in the traffic filter 0.0.0.0/0 which is perhaps a bit counter to setting up the PrivateLink in the first place.

Then you could use the cloud.id

Hope that helps

1 Like