Relationships
#4081 Support scoped observer identities with vault-backed access keys
Opened by lint · 10/28/2026· Shipped 10/28/2026
A recurring read-only AWS observer needs a dedicated machine identity rather than an expiring interactive SSO session. The installed IAM user type lacks typed access-key provisioning and safe vault publication. Please consider a method that plans narrowly scoped inline read policies, verifies exact account and owned user tags/path, refuses foreign policies/groups/keys, creates at most one key, saves recovery material privately before publishing, verifies caller identity and permitted reads, and stores credentials through a vault without exposing secrets in resources, logs or arguments. Idempotent recovery should reuse the owned key and never rotate unrelated keys. We currently extend the official user type locally with pinned AWS SDK APIs. This is a capability request; no user data or production credentials are attached.
Upstream repository: https://github.com/swamp-club/swamp-extensions
Environment
- Extension:
@swamp/aws/iam@2026.10.25.1 - swamp:
20260909.131252.0-sha.375d7eca - OS:
linux(x86_64) - Deno:
2.9.6 - Shell:
/bin/bash
Shipped
Click a lifecycle step above to view its details.
system commented 10/28/2026, 4:38:22 PM
Classified automatically when this issue was filed.
- Source: Extensions
If you feel this classification is incorrect, add a ripple to tell us so.
stack72 commented 10/28/2026, 11:19:45 PM
Thanks @lint for reporting this! We shipped: Add two native-SDK custom methods to the generated @swamp/aws/iam user model via a new codegen/aws/enrichments/iam-user enrichment. provisionAccessKey verifies the account and the owned path and tags, refuses attachments outside a declared-plus-allowed list and refuses foreign keys, creates at most one tag-owned access key (with a concurrent-run guard), writes the secret to a sensitive vault-backed field and reads it back, rolls back the key on any write failure, and on reuse verifies the stored secret is recoverable before reporting success. verifyAccessKey checks caller identity with the provisioned key and runs SimulatePrincipalPolicy for permitted and denied actions. An opt-in ownsResourceWrite generator flag gives a custom function a narrow read and write handle for its own output resource.. The fix has been merged and a release is on its way. We appreciate your contribution to swamp.
Sign in to post a ripple.