This is the most technically sophisticated canary in Snare. It fires at credential resolution time — before the AWS SDK makes a single network request. CloudTrail never sees it.
How it works
When an agent runsaws s3 ls --profile prod-admin, the AWS SDK must first resolve credentials for that profile. For profiles using source_profile, it follows the chain to the source and runs the credential_process command.
That’s where Snare fires.
The two-profile pattern
The canary uses an assume-role pattern that looks like a real staging/production setup:~/.aws/config
~/.aws/config sees a realistic assume-role profile. The credential_process source profile is named consistently and hidden below.
Why CloudTrail can’t see this
AWS CloudTrail logs API calls to AWS services.credential_process runs entirely locally — it’s a shell command executed by the SDK before any network request. CloudTrail only sees the subsequent API call (which fails with invalid credentials).
Snare fires at step T+0.01s. CloudTrail’s first entry would be at T+0.03s, after the credentials have already been used.
Air-gapped / network-restricted environments
If the callback URL is unreachable (firewall, air-gap),curl fails silently. The shell command still outputs the fake JSON credentials — the agent receives apparently-valid credentials and continues unaware.
For fully air-gapped environments, use self-hosted mode to point callbacks at an internal server.
Precision mode
awsproc is one of three canaries included in snare arm --precision:
False positive risk
Essentially zero.awsproc only fires when something actively attempts to resolve credentials using that specific profile. A legitimate agent configured to use prod-admin wouldn’t be in your environment unless you put it there.