o11y-auth

You can authenticate to TiDB Cloud O11Y APIs by using a unified credential retrieval process that fetches all required bearer tokens, Auth0 control plane tokens, and AWS STS S3 credentials in a single call. This eliminates manual token collection and includes automatic caching to prevent repeated logins.

To map TiDB cluster deploy types to O11Y bizType values, you can use a deterministic built-in helper that automatically converts cluster deploy types like premium, dedicated, or starter alongside their environments into the correct bizType for your API endpoints.

Yes, the O11Y authentication process caches AWS STS credentials and Auth0 tokens automatically. It uses cached auto-refreshing credentials with built-in retry logic to handle transient authentication failures and avoid repeated logins.

To retrieve S3 bucket access credentials for TiDB Cloud exported data, you need curl and jq installed in your environment. The unified authentication call fetches the required AWS STS S3 credentials alongside your O11Y bearer tokens.

TiDB Cloud O11Y authentication may fail with transient token errors due to network disruptions or token expiration. The unified authentication process includes automatic retry logic specifically designed to handle these transient authentication failures.