Secrets vault integration

Argent with AWS Secrets Manager

Keep your AI provider keys in AWS Secrets Manager. Argent fetches each secret at the moment a request needs it and attaches it at the gateway, so by default the agents that work through Argent never hold it.

AWS Secrets Manager logo
01 / SECRETS VAULT INTEGRATION

What Argent does with AWS Secrets Manager

Your AI provider keys stay in AWS Secrets Manager, where your security team already manages them. Argent keeps a reference to each key, not a copy, and reads the value at the moment a request needs it.

  • Agents hold their own Argent key, not yours. By default, the agents that work through Argent never hold the provider's key. Each agent gets its own Argent key, and the gateway attaches the real key from AWS Secrets Manager on the way out. See keyless agents.
  • Why it matters. GitGuardian counted 1,275,105 leaked AI-service secrets in 2025, up 81% in a year. A key that lives only in your vault is not sitting in every agent's settings file.
  • One place to change a key. Rotate it in AWS Secrets Manager or from the Argent console. No agent needs a new setting, because by default no agent holds it.
  • More than AI keys. Argent stores the other credentials it uses the same way, as vault references and never as values: MCP server credentials, ticketing tokens and directory sign-ins.
  • It can stay on the AWS network. When Argent runs in your VPC, enter a Secrets Manager VPC endpoint as the endpoint override and list the endpoint's subnet range in ARGENT_TENANT_EGRESS_PRIVATE_CIDRS. AWS states that traffic between your VPC and Secrets Manager through such an endpoint does not leave the AWS network (AWS).
02 / SECRETS VAULT INTEGRATION

How a request gets its key from AWS Secrets Manager

The agent points its AI client at the Argent gateway and sends its own Argent key. The rest happens at the gateway, on every AI model call.

  1. Argent checks who is calling. The Argent key must belong to an active agent. The Argent key stops at the gateway: the AI provider never receives it.
  2. Argent checks the agent may use the credential. A credential can require a permission, and an agent without it is refused.
  3. Argent finds the vault that serves the reference. Each credential points at a reference, and each reference belongs to one connected vault.
  4. Argent fetches the secret from Secrets Manager. It retrieves the secret by the id or ARN the reference names, with requests signed by the IAM credentials you gave it.
  5. Argent swaps the keys. It removes any provider key the agent sent and attaches the key from AWS Secrets Manager on the way out to the provider.
  6. Argent signs a record. It names the agent, the provider and the vault reference. It never contains the key.

Argent holds the value only briefly, in a cache kept separate for each tenant and vault, and overwrites it when it is dropped. If anything fails, the request is refused with a named reason, such as credbroker.vault_unavailable. A customer vault never falls back to another vault, and a failed vault never falls back to the agent's own key.

03 / SECRETS VAULT INTEGRATION

What you enter in the Argent console

An admin connects AWS Secrets Manager under Integrations > Vault in the Argent console. The form asks for:

FieldWhat it is
RegionThe AWS region your secrets are in, for example us-east-1.
Endpoint overrideOptional. A VPC or PrivateLink endpoint address. Empty uses the default regional endpoint.
Canary secret idOptional. A secret the connection test retrieves to prove read access. The test never returns the value.
IAM credentials referenceWhere the access key pair Argent signs with is kept, never the keys themselves.

The credential Argent signs in with is itself a reference. The IAM access key pair is kept in Argent's built-in vault, resolved only when the connector connects, and never stored in Argent's database, logged or shown back.

  • Test. Tick the live check on the form and Test signs in and, with a canary secret set, reads it, then reports reachable or unreachable without returning the value. Without the live check, Test checks the settings only.
  • Connect, see impact, disconnect. The same page connects the vault, shows what depends on it, and disconnects it.
  • Pick, do not type. Reference fields across the console offer a picker of the references the deployment already holds, so nobody mistypes a path.
04 / SECRETS VAULT INTEGRATION

What you set up on the AWS Secrets Manager side

A few things on your side, once. Your team keeps managing the keys exactly where it does today.

  • An IAM identity for Argent allowed secretsmanager:GetSecretValue on the secrets Argent will use, plus kms:Decrypt on the key when a secret is encrypted with a customer-managed key, as AWS documents.
  • Its access key pair, saved as one reference. Store {"access_key_id": ..., "secret_access_key": ...} in Argent's built-in vault and give Argent the reference.
  • A canary secret, or permission to list. With a canary secret id, the test retrieves it. With none, the test lists secrets, which needs secretsmanager:ListSecrets.
  • Optional: an interface VPC endpoint for Secrets Manager, entered as the endpoint override, with its subnet range listed as described in the next point.
  • A network path from Argent. Argent dials every connector through a guarded client that refuses private, loopback and link-local addresses unless told otherwise. If your vault sits on a private network, an operator lists its address range in the ARGENT_TENANT_EGRESS_PRIVATE_CIDRS setting (Helm value controlPlane.tenantEgressPrivateCidrs). Cloud metadata addresses are refused whatever is listed.
  • Writing is a separate choice. To rotate keys from the Argent console, an admin turns on writing for this vault, with its own sign-in for writes. Until then Argent only reads.
05 / SECRETS VAULT INTEGRATION

Guardrails around your vault

Connecting a vault to an AI gateway should not widen who can reach its keys. These rules hold for AWS Secrets Manager:

GuardrailWhat happens
Fails closedA vault that cannot be reached, a missing credential or an empty secret refuses the request with a named reason. Nothing is sent without the right key.
Tenant fenceA tenant admin can only name references inside its own tenant's area. Another tenant's path is refused and signed.
Read-only until you say soWriting is off by default. Turning it on takes a fresh passkey confirmation and is recorded.
A second vault, by pathA tenant can connect a second vault that owns a path prefix. Each reference goes to the vault whose path matches it most closely; anything else goes to the default vault. If that vault is down, its requests are refused, never sent elsewhere.
Signed changesChanging which paths a vault serves is a signed change. If the signed record cannot be written, the change is refused.
Signed useEvery request's record names the agent, the provider and the vault reference, never the key.

Rotating a key. From the Credential Broker page, Argent writes the new value to AWS Secrets Manager, then the admin keeps it or rolls it back. After rotating a key directly in AWS Secrets Manager, run argentctl secrets rotated so every gateway drops its cached copy. Revoking a credential in Argent drops Argent's reference; the value stays in AWS Secrets Manager.

What the operator sees. The Credential Broker page lists every connected vault and reference, which agents used each secret, their human owners and the last five calls. When an auditor asks which agents used the company's AI key, the record answers. See one-click audit evidence.

06 / SECRETS VAULT INTEGRATION

Where it fits, and how you start

A vault integration is where keyless agents start.

  1. Watch. In Watch mode an agent's own key passes untouched, and Argent records what it would have stripped or refused.
  2. Connect AWS Secrets Manager. Fill in the form under Integrations > Vault and run Test.
  3. Point credentials at it. Add each AI provider credential as a reference to the secret already in AWS Secrets Manager. Argent records the reference; it never copies the value.
  4. Enforce and prove. Switch on Enforce, give each agent its own Argent key, and retire the old copies. Every request's record shows which agent used which key.
Secrets vaults Argent connects to

Your AI provider keys can live in any of these, or in the vault built into Argent.

  • HashiCorp Vault and OpenBao
  • AWS Secrets Manager
  • CyberArk Conjur
  • Infisical