> ## Documentation Index
> Fetch the complete documentation index at: https://docs.valkyrie.vals.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure sandbox providers

> Store sandbox-provider credentials and select a provider for runs.

Valkyrie resolves sandbox-provider credentials from AWS Secrets Manager. Register each secret under a provider name in the CLI configuration. Full syntax is in the [`config provider set`](/reference/cli/config#provider-set) and [`config provider default`](/reference/cli/config#provider-default) reference.

## Daytona

1. [Create a Daytona API key](https://app.daytona.io/dashboard/keys) with read, write, and delete access to sandboxes and snapshots.
2. Choose a target from Daytona's [shared regions](https://www.daytona.io/docs/regions#shared-regions).
3. Store the following JSON as an AWS Secrets Manager secret:

```json theme={null}
{
  "DAYTONA_API_KEY": "...",
  "DAYTONA_API_URL": "https://app.daytona.io/api",
  "DAYTONA_TARGET": "..."
}
```

Register the secret:

```bash theme={null}
valkyrie config provider set daytona DaytonaSecrets
```

The first configured provider becomes the default. Set the default explicitly with:

```bash theme={null}
valkyrie config provider default daytona
```

Select a configured provider for one run:

```bash theme={null}
valkyrie run start --agent sweagent --benchmark swebench --provider daytona
```

Provider secret schemas are provider-specific. Registering a name does not make one provider's secret shape valid for another provider.

The legacy `DAYTONA_SECRET_NAME` configuration key remains supported only when `sandbox_providers` is not configured.