AWS

Alfred-OS uses AWS for two optional things: Secrets Manager (Slack webhook, Sentry tokens, third-party API keys) and per-agent IAM (one scoped IAM identity per scheduled agent).

If you don’t need either, skip this. Put SLACK_WEBHOOK_URL in ~/.alfredrc directly. The framework runs fine without an AWS account.

Full guide at docs/AWS_SETUP.md. Highlights:

Why per-agent IAM

The operator’s SSO has admin everywhere. If a scheduled agent inherited that, a runaway prompt could in principle trigger any AWS action. Per-agent IAM caps blast radius:

• <your-codename>-cron: read-only on the agent’s specific secrets (test creds, webhooks, etc.).
• gordon-cron: read-only on ECS, ALB, CloudWatch logs/metrics, plus the Sentry token.
• alfred-host: read-only on alfred/* secrets.

Agent runners that touch AWS read role-specific variables such as ALFRED_HUNTRESS_AWS_PROFILE or ALFRED_GORDON_AWS_PROFILE from ~/.alfredrc, then strip ambient AWS_* credentials and set AWS_PROFILE only for the AWS subprocess they own.

Create a scoped IAM user

AWS_ADMIN_PROFILE="<your-admin>"

aws --profile "$AWS_ADMIN_PROFILE" iam create-user \
  --user-name <your-codename>-cron \
  --tags Key=purpose,Value=alfred-os-agent

aws --profile "$AWS_ADMIN_PROFILE" iam create-access-key \
  --user-name <your-codename>-cron --output json > /tmp/keys.json

# Copy AccessKeyId + SecretAccessKey into ~/.aws/credentials, then:
shred -u /tmp/keys.json

~/.aws/credentials entry:

[<your-codename>-cron]
aws_access_key_id = AKIA...
aws_secret_access_key = ...
region = us-east-1

Attach a scoped inline policy

aws --profile "$AWS_ADMIN_PROFILE" iam put-user-policy \
  --user-name <your-codename>-cron \
  --policy-name <your-codename>-cron-secrets-readonly \
  --policy-document file:///tmp/policy.json

Policy templates for Slack reader, ECS read-only, CloudWatch logs etc. live in docs/AWS_SETUP.md.

Secret naming convention

Path	What it holds
alfred/slack-webhook	Slack incoming webhook URL
alfred/slack-bot-token	Slack xoxb- token (when ready)
alfred/slack-app-token	Slack xapp-1- token for Socket Mode
alfred/sentry-dsn-agents	Sentry DSN agent runners post events to
alfred/sentry-api-token	Sentry API token for query operations

The secret ID prefix alfred/ is the default convention. Adjust to your fleet’s naming if you prefer (e.g. myfleet/slack-webhook). Override SLACK_WEBHOOK_SECRET_ID in ~/.alfredrc to match.

Key rotation

Every 90 days minimum. Mint new key → update ~/.aws/credentials → verify with aws sts get-caller-identity → delete old key. See the runbook in docs/AWS_SETUP.md.

Troubleshooting

• AccessDeniedException on a specific action: policy doesn’t grant it. Check the error for the exact ARN + action.
• Operator’s SSO env vars override the agent’s profile: run under launchd (no operator env inherited) or strip env at the top of the runner.
• AccessDeniedException on a secret you can clearly read: resource pattern needs * suffix to match the 6-char secret ID suffix (alfred/slack-webhook-NmY0Gv).