Use when the user wants to list available PrivateLink endpoint services, list/create/delete PrivateLink endpoints for a project, or manage the endpoint whitelist on Zilliz Cloud.
Use when the user wants to list available PrivateLink endpoint services, list/create/delete PrivateLink endpoints for a project, or manage the endpoint whitelist on Zilliz Cloud.
Prerequisites
CLI installed and logged in (see setup skill).
A project to attach endpoints to (see project-region skill).
PrivateLink lets a cluster be reached over a cloud-provider private network (AWS PrivateLink, GCP Private Service Connect, Azure Private Link) instead of the public internet. Endpoints are scoped to a project and a region.
Workflow for a new endpoint:
zilliz privatelink list-services --region-id <region> to find the endpointService value for that region (and whether whitelistRequired is true).
If whitelistRequired is true, call zilliz privatelink add-whitelist --project-id <id> --region-id <region> first so the project is allowed to attach an endpoint in that region.
Create the VPC endpoint in your own cloud account (out-of-band, in the AWS/GCP/Azure console or via IaC) and capture its endpoint ID (e.g. vpce-xxxx).
Register it with zilliz privatelink create --project-id <id> --region-id <region> --endpoint-id <vpce-id>. For GCP, also pass --gcp-project-id <gcp-project>.
list is per-project: zilliz privatelink list --project-id <id>. There is no global listing.
delete is irreversible -- always confirm with the user, especially in production. Existing connections from that endpoint stop working immediately.
After enabling PrivateLink for a cluster, the cluster's endpoint URL switches to the private DNS form. Re-run zilliz cluster describe --cluster-id <id> to fetch the updated endpoint and update any consumer config.