Credential loss investigation for AWS org project
Investigate why task <https://app.jaah.ai/tasks/10261> was unable to use cred org/projects/oam/aws which has always been there. When I pasted the secret key again it is working now. How did that cred get lost?
Outcome
Root cause: nothing was lost. The Jaah row was unchanged and the IAM key was never revoked. 10261's failing call used h1's stale `optic` AWS profile (the OAM seed scripts pass --profile, which beats the broker keys). Report uploaded; follow-ups named, not filed. Memory: none applied.
Artifacts
Activity
- Created
- Run
- Runner started
- Awaiting response
- Awaiting response
- Awaiting response
- Awaiting response
- Awaiting response
- Runner resumed
- Runner ended (done)