Create access key from container credentials
Mint short-lived credentials for in-cluster workloads using the AWS container-credentials provider shape.
gRPC method: CreateAccessKeyFromContainerCreds
- The API server is
https://api.coreweave.com. - This endpoint uses the
ContainerCredentialsAuthscheme: send a raw JWT/OIDC token as theAuthorizationheader value, with noBearerprefix. This shape matches the AWS container-credentials provider for in-cluster workloads.
AccessKeyId,
SecretAccessKey, Token, Expiration) so existing AWS
SDKs and tooling that consume the
AWS_CONTAINER_CREDENTIALS_FULL_URI environment variable
can adopt it without code changes.
Substitute {orgId} with your organization ID.
Authorizations
Raw JWT/OIDC token sent as the Authorization header value with no Bearer prefix. Only used by GET /v1/cwobject/temporary-credentials/oidc/{orgId} for the AWS-style container-credentials provider.
Path Parameters
Response
OK
AWS-compatible container-credentials response shape. The property names use PascalCase (AccessKeyId, SecretAccessKey, Token, Expiration) so existing AWS SDKs and tooling that consume AWS_CONTAINER_CREDENTIALS_FULL_URI can adopt this endpoint without code changes. This is intentional and differs from every other endpoint, which uses camelCase.
The access-key ID.
The secret access key. Treat as a credential.
An optional session token. May be empty for non-session credentials.
The expiration time of the credentials.
Free-form caller-supplied attributes attached to the key (for example, name).
Free-form caller-supplied multi-valued attributes attached to the key. Each value is an AttributeList (an array of strings).