← ZillizCONTENT HISTORY

Update to Zilliz

Snapshot Sep 30, 2026 · 23:15 UTC · version 1.4.4

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "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.",
  "included_files": [],
  "name": "privatelink",
  "skill_md_contents": "---\nname: privatelink\ndescription: 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.\n---\n\n## Prerequisites\n\n1. CLI installed and logged in (see setup skill).\n2. A project to attach endpoints to (see project-region skill).\n\n## Commands Reference\n\n### List available PrivateLink endpoint services\n\n```bash\nzilliz privatelink list-services\n# Optional: --region-id <filter-by-cloud-region>\n```\n\n### List Privatelinks\n\n```bash\nzilliz privatelink list --project-id <project-id>\n```\n\n### Create a Privatelink\n\n```bash\nzilliz privatelink create \\\n  --project-id <project-id> \\\n  --region-id <cloud-region> \\\n  --endpoint-id <vpc-endpoint-id>\n# Optional: --gcp-project-id <gcp-project-id>\n```\n\n### Delete a Privatelink\n\n```bash\nzilliz privatelink delete --project-id <project-id> --endpoint-id <endpoint-id-to-delete>\n```\n\n### Add region to PrivateLink endpoint whitelist\n\n```bash\nzilliz privatelink add-whitelist --project-id <project-id> --region-id <cloud-region-to-whitelist>\n```\n\n## Guidance\n\n- 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.\n- Workflow for a new endpoint:\n  1. `zilliz privatelink list-services --region-id <region>` to find the `endpointService` value for that region (and whether `whitelistRequired` is true).\n  2. 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.\n  3. 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`).\n  4. 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>`.\n- `list` is per-project: `zilliz privatelink list --project-id <id>`. There is no global listing.\n- `delete` is irreversible -- always confirm with the user, especially in production. Existing connections from that endpoint stop working immediately.\n- 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.\n"
}

SHA-256 of public snapshot: a614ac9b41769225a9a9c6559a0bb320a21781048305330a3074f181cd04e68a