> For the complete documentation index, see [llms.txt](https://docs.firefly.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.firefly.ai/detailed-guides/oidc-provider.md).

# OIDC Provider

Firefly can authenticate to your cloud provider using OpenID Connect (OIDC) instead of long-lived static credentials. At execution time Firefly issues a short-lived OIDC token, your cloud provider exchanges it for temporary credentials, and the run proceeds under an identity you control. No static cloud key is ever stored by Firefly.

Setup always has two parts: registering Firefly as an identity provider in your cloud account, then enabling OIDC on the Firefly project or workspace.

## Choose your cloud provider

* [Amazon Web Services (AWS)](/detailed-guides/oidc-provider/aws.md) — register Firefly as an IAM identity provider and assume an IAM role via web identity.
* [Google Cloud](/detailed-guides/oidc-provider/google-cloud.md) — register Firefly as an OIDC provider in a workload identity pool and impersonate a service account via Workload Identity Federation.

## Where OIDC is configured in Firefly

For both providers, OIDC can be enabled at either level:

* **Project level** — an inherited attribute. All sub-projects and workspaces within the project pick up the same authentication configuration.
* **Workspace level** — configured per workspace under **Workspace Configuration → Runner Configuration**, and overrides what the project provides.

Each provider guide covers the specific values you need to enter.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.firefly.ai/detailed-guides/oidc-provider.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.