Milvus

Overview

Use Milvus credentials to make authenticated API calls through Alter Vault without exposing API keys in code.

Property	Value
Provider ID	milvus
Category	AI
Credential Type	API Key

Step 1: Get Credentials

Log in to Zilliz Cloud

Log in to Zilliz Cloud (hosted Milvus).

Create an API key

Open API Keys and create a key for the organization or project.

Copy the key

Copy the key — it is only shown once.

Warning

Never share credentials publicly. Store them securely and only enter them in the Alter Vault Developer Portal.

Step 2: Add to Alter Vault

Open the Developer Portal

Go to portal.alterauth.com and navigate to the application.

Add Milvus

Go to Managed Secrets > Add Provider > Milvus.

Enter credentials

Paste your API Key into the credential field.

Enter the deployment endpoint

Paste your Cluster public endpoint — copy it from the Zilliz Cloud console’s cluster details. Alter derives this credential’s allowed hosts from that exact host, so proxied calls can only ever reach your deployment. The allowlist cannot be widened or edited separately; rotate the credential with a new endpoint to retarget it.

Save

Click Save. You’ll receive a grant_id to use with the SDK.

Using in Code

response = await alter_app.request(
    HttpMethod.POST,
    "https://YOUR-CLUSTER.cloud.zilliz.com/v2/vectordb/entities/search",
    grant_id="YOUR_GRANT_ID",
    json={
        "collectionName": "my_collection",
        "data": [[0.05, 0.61, 0.76, 0.74]],
        "limit": 5,
    },
)

Notes

• Self-hosted Milvus accepts username:password as the bearer value on the RESTful API.

Policy-cataloged operations

Alter policy rules can target these attested operations and families for operation-level and parameter-aware controls.

Operation ID	Families	Method	Provider path
aliases/create	write	POST	/v2/vectordb/aliases/create
aliases/list	read	POST	/v2/vectordb/aliases/list
collections/create	write	POST	/v2/vectordb/collections/create
collections/describe	read	POST	/v2/vectordb/collections/describe
collections/drop	delete	POST	/v2/vectordb/collections/drop
collections/get_load_state	read	POST	/v2/vectordb/collections/get_load_state
collections/get_stats	read	POST	/v2/vectordb/collections/get_stats
collections/has	read	POST	/v2/vectordb/collections/has
collections/list	read	POST	/v2/vectordb/collections/list
collections/load	write	POST	/v2/vectordb/collections/load
collections/release	write	POST	/v2/vectordb/collections/release
collections/rename	write	POST	/v2/vectordb/collections/rename
databases/create	write	POST	/v2/vectordb/databases/create
databases/list	read	POST	/v2/vectordb/databases/list
entities/delete	delete	POST	/v2/vectordb/entities/delete
entities/get	read	POST	/v2/vectordb/entities/get
entities/hybrid_search	read	POST	/v2/vectordb/entities/hybrid_search
entities/insert	write	POST	/v2/vectordb/entities/insert
entities/query	read	POST	/v2/vectordb/entities/query
entities/search	read	POST	/v2/vectordb/entities/search
entities/upsert	write	POST	/v2/vectordb/entities/upsert
indexes/create	write	POST	/v2/vectordb/indexes/create
indexes/describe	read	POST	/v2/vectordb/indexes/describe
indexes/drop	delete	POST	/v2/vectordb/indexes/drop
indexes/list	read	POST	/v2/vectordb/indexes/list
partitions/create	write	POST	/v2/vectordb/partitions/create
partitions/drop	delete	POST	/v2/vectordb/partitions/drop
partitions/list	read	POST	/v2/vectordb/partitions/list
partitions/load	write	POST	/v2/vectordb/partitions/load
partitions/release	write	POST	/v2/vectordb/partitions/release