Skip to main content
← Back to list
01Issue
FeatureShippedExtensions
Assigneesstack72

#228 Detect AWS CredentialsProviderError in @swamp/aws-sm-vault and prepend SSO-expiration hint

Opened by stack72 Β· 5/4/2026Β· Shipped 5/6/2026

Follow-up to swamp-club#226 (which addresses the same problem in @swamp/s3-datastore and @swamp/gcs-datastore).

The aws-sm vault wraps the AWS SDK and would surface the same CredentialsProviderError discoverability issue when a user's SSO session expires mid-secret-fetch. Currently vault/aws-sm/extensions/vaults/aws_sm.ts has no wrapError pattern β€” auth failures surface as raw SDK errors with the Token-is-expired hint buried in a stack trace.

Apply the same treatment as #226 to the secret-fetch path: detect CredentialsProviderError / ExpiredTokenException / InvalidAccessKeyId / SignatureDoesNotMatch / 403 AccessDenied, and prepend a swamp-flavoured 'Vault session expired' / 'Vault credentials rejected' summary line that names the cause and points to 'aws sso login --profile ' (reading AWS_PROFILE from env).

Note: aws-sm currently has no error-wrapper class equivalent to S3OperationError. The implementation will need to introduce one, mirroring the pattern from datastore/s3/extensions/datastores/_lib/s3_client.ts. Bigger lift than #226 β€” that's why it's split out.

02Bog Flow
βœ“OPENβœ“TRIAGEDβœ“IN PROGRESSβœ“SHIPPED+ 1 MOREASSIGNED+ 8 MOREREVIEW+ 3 MOREPR_MERGEDSHIPPED

Shipped

5/6/2026, 10:30:43 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack725/4/2026, 10:44:37 PM

Sign in to post a ripple.