Skip to main content
← Back to list
01Issue
FeatureOpenExtensionsPublic
AssigneesNone

Relationships

#2099 aws-sm vault: support profile config key to select named AWS credential profiles

Opened by stack72 · 9/10/2026

Description

The aws-sm vault provider always constructs its SecretsManagerClient with only { region }, so credentials always come from the default AWS credential chain. There is no way to specify a named AWS profile in the vault config.

Teams where engineers use different profile names in ~/.aws/config (e.g. Developer-xero-ps-sre-test) have no way to pin a vault to a specific profile — the vault silently uses whichever profile the default chain resolves to.

Suggested approach

Add an optional profile key to the aws-sm configSchema:

configSchema: z.object({
  region: z.string().min(1).describe("AWS region..."),
  profile: z.string().optional().describe("Named AWS profile from ~/.aws/config"),
}).strict(),

Then pass it to the SecretsManagerClient via the credentials option or AWS_PROFILE-equivalent configuration so the vault uses the specified profile's credentials.

Context

Issue #2095 fixed the silent key-stripping bug — unknown config keys like profile now correctly error. This follow-up adds profile as a recognized, functional config key.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED

Open

9/10/2026, 2:13:43 PM

No activity in this phase yet.

03Sludge Pulse

Sign in to post a ripple.