Ben Kehoe Portfolio
AWS Serverless Hero maintaining a set of widely-used open-source tools (aws-assume-role-lib, aws-export-credentials, aws-error-utils) that solve real cross-account IAM and credential-handling problems encountered while architecting serverless systems at scale.
What makes it work
A breakdown of the choices that make this portfolio stand out.
Small, single-purpose tools that fix a specific operational pain point
Each repository (assume-role chaining, credential export, error handling) solves one concrete AWS IAM annoyance that shows up repeatedly in serverless architecture work, rather than proposing a general-purpose framework.
A day job and title stated plainly alongside the open-source work
Listing the current employer directly on the profile grounds the tooling in ongoing, practical use rather than presenting it as abandoned side projects.
Adoption signals left visible rather than asserted
Star counts, forks, and GitHub achievement badges are left as public, checkable numbers rather than a claimed "widely used" line — the evidence is inspectable rather than asserted.
What Cloud Architects can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
Ship small, single-purpose tools that fix one specific pain point in your domain — focused utility is easier for others to adopt and evaluate than a broad framework.
Keep your current role visible next to your open-source work so visitors can see the tools are informed by ongoing, real production use.
Let adoption metrics (stars, forks, issues closed) speak for themselves instead of writing marketing claims about your tools' popularity.
More Cloud Architect portfolios
Ready to build your portfolio?
Follow the Cloud Architect roadmap — skills, projects, and timeline to get hired.