Securing Endpoints
NVIDIA CCluster does not expose public endpoints. Every LLM Serving and General Inference deployment must be protected, and clients must authenticate on each request. You secure a deployment with at least one of the following:
- Bearer token — an
Authorization: Bearer <token>header on each request. - mTLS client certificate — a TLS certificate the client presents on each request.
Endpoint bearer tokens (from your Vault) are not the same as service account credentials. Service accounts authenticate automation to NVIDIA CCluster platform APIs; Vault bearer tokens protect calls to your deployed endpoints.
You choose the protection method when configuring a deployment. You may enable both for defense in depth.
Bearer token access
Generate a Bearer token from your Vault, then include it in the Authorization header of every request.
Using curl command
Using OpenAI client library
mTLS certificate access
Select the Make it a private endpoint? option when configuring a deployment. This generates a TLS certificate upon deployment, which you can download. Access to the endpoint will then require the http client to use this certificate. Here are a few examples:
Using curl command
Using httpx library
Using OpenAPI client library