Dagger secret providers support AWS Secrets Manager and Parameter Store
Introduced 2026-02-05 · score 0.95
HOW TO USE IT
When a Dagger function accepts a `Secret`, pass an AWS secret URI for its argument: use `aws+sm://` for Secrets Manager or `aws+ps://` for Parameter Store.
dagger call <function> --<secret-argument>=aws+sm://<secret-name>dagger call <function> --<secret-argument>=aws+ps://<parameter-name>WHY THIS HELPS
Supply an AWS-managed secret to a Dagger function while building or testing repository code.
REQUIREMENTS AND LIMITATIONS
- Version: v0.19.11
- <function> (required): Dagger function name; replace with the function that accepts the secret.
- --<secret-argument> (required): Named CLI argument corresponding to the function's `Secret` parameter.
- aws+sm://<secret-name> (required): URI scheme and secret name for AWS Secrets Manager.
- aws+ps://<parameter-name> (required): URI scheme and parameter name for AWS Systems Manager Parameter Store.
- Prerequisite: Configure AWS credentials through environment variables, the shared credentials file (`~/.aws/credentials`), or IAM role credentials.
- Prerequisite: Set the `AWS_REGION` environment variable.
FIRST-PARTY EVIDENCE
- https://github.com/dagger/dagger/releases/tag/v0.19.11
- https://github.com/dagger/dagger/pull/11728
- https://docs.dagger.io/0.20/getting-started/types/secret/
Check the installed version and the source before using it. Entry JSON