The addresses had no dates
A release token showed up in use from four machines in AWS that I couldn't account for. Two hours later it turned out to be my own runner fleet, and I'd fixed the real problem anyway.

A release token showed up in use from four machines in AWS that I couldn't account for. Two hours later it turned out to be my own runner fleet, and I'd fixed the real problem anyway.

Publish an OpenPGP certificate a researcher can encrypt to, and read what they send, without a private key ever existing in your process.

The homelab finally ran out. Not disk this time, capacity. So the overflow went to AWS, on the condition that it costs nothing when nobody's pushing.

Setting up an AWS billing alarm before you need one, with a KMS gotcha in the middle that stops the alert ever reaching you.

A fresh AWS account cannot enable GuardDuty or Security Hub without a subscription, so the security baseline failed on the account it protects.

A GitLab to AWS OIDC trust policy kept returning 403, and no IAM change fixed it: the policy matched a claim GitLab never actually asserts.

Routing AWS GuardDuty and Security Hub findings so an alert still means something: forward high severity only, and drop the duplicates.

Applying a security baseline to a fresh AWS account: audit logging, config recording, threat detection and an operator role that is not root.

Replacing long-lived AWS access keys in CI with OIDC federation, so the pipeline mints a short-lived token instead of holding a secret.

AWS tagging in two layers: account-wide invariants on the provider default tags, resource specifics in the module, and which one wins on a clash.
