GitHub Actions + Terraform CI/CD for AWS Lambda with OIDC
My GitHub Actions pipeline for AWS Lambda and Terraform: OIDC deploys with no stored AWS keys, S3 state locking, a prod approval gate, and alias rollback.
CI, infrastructure as code, and a release path the team can run without me in the room.
I use the tools that fit the stack you already have.
I fit the pipeline to the repo and the deploy you already use.
The point is a release your team can run without me in the room.
I track how often you ship, how long a change takes, and how often it fails.
These are the tools I use when they fit the job.
Nagios
Splunk
Nagios
SplunkWriting
Posts that sit next to this work.
My GitHub Actions pipeline for AWS Lambda and Terraform: OIDC deploys with no stored AWS keys, S3 state locking, a prod approval gate, and alias rollback.
One Claude Code Session Isn't Enough Anymore I love a single Claude Code session. It's where most of my real work happens, plan in one pane, code in the other, terminal humming along. But here's the t
How I use AI as a first-pass reviewer for Terraform and Lambda pull requests, while keeping human judgment on the risky parts