Skip to main content
GitHub Actions workflows can authenticate to CoreWeave AI Object Storage using GitHub’s OIDC tokens. This eliminates the need to store static credentials as repository secrets.

Use within a workflow

The following example workflow uses the coreweave/actions-public/auth/caios-login GitHub Action to configure AI Object Storage access as an AWS profile, then lists the buckets the workflow can access. Replace [ORG-ID] with your CoreWeave organization ID.

Example IAM policies

Before a GitHub Actions workflow can access AI Object Storage, you must grant the workflow’s OIDC identity permission through an organization access policy. The following examples show how to allow full access to all repositories in a GitHub organization, using either JSON or Terraform.
Always use the organization name with a trailing slash (/) in the role/ bindings when using GitHub Actions. For example, role/https://token.actions.githubusercontent.com:repo:octo-org/* is safe, but role/https://token.actions.githubusercontent.com:repo:octo-org* is unsafe because an organization named octo-org-hacks could match.
Last modified on May 29, 2026