Release
v1.6.0
vault keeperResolve Argus' secrets from AWS Secrets Manager using your pod's IAM identity — no secrets in environment variables — through a pluggable provider model.
Highlights
- 01
AWS Secrets Manager, IAM-native
On EKS, Argus reads registry credentials and the GitLab token straight from AWS Secrets Manager using the pod's IRSA / Pod Identity, optionally assuming a role. Point it at one JSON secret with ARGUS_AWS_SECRET_ARN and reference keys by name.
Read the guide → - 02
One reference syntax, any secret
${{secret:gitlab-token}} pulls a key from the bundle, ${{aws-secretsmanager:id#key}} names a specific secret, and ${{ENV_VAR}} still reads the environment — the same forms work in config.yml and env values alike.
Read the guide → - 03
Built to take more clouds
Secret resolution sits on a pluggable provider model. AWS is first; GCP Secret Manager, Azure Key Vault, and HashiCorp Vault can be added without changing the reference syntax or your configuration.
Read the guide →
Full notes
Added
- AWS Secrets Manager secret backend: resolve
config.ymlregistry credentials and theGITLAB_PRIVATE_TOKENfrom Secrets Manager via the pod's IAM identity (IRSA / Pod Identity).ARGUS_AWS_ROLE_ARNassumes a role via STS;ARGUS_AWS_SECRET_ARNnames the JSON bundle secret backing${{secret:KEY}}. References (${{secret:key}},${{aws-secretsmanager:id#key}},${{ENV_VAR}}) work in both config.yml and env values. Secret values are never logged. - Pluggable secret-provider model (ADR-021): AWS is the first provider; the AWS SDK is isolated to one subpackage and initialised lazily, so non-AWS users pay nothing at runtime. GCP, Azure, and Vault can be added without changing the reference syntax.
- New Secrets documentation page and
aws_role_arn/aws_secret_arninputs on the GitLab CI/CD component.
Changed
- Updated the GitLab CI/CD component and documentation examples to default to Argus
1.6.0.