Messy workflow
Identify what is manual, risky, unclear, duplicated, slow, or dependent on tribal knowledge.
Aiden Rhaa
Product-Minded AWS Infrastructure EngineerAWS Cloud Engineer · Infrastructure Automation · Platform Engineering
I build cloud systems for real business workflows.
I design secure AWS infrastructure, automation, and internal platforms that reduce manual work, improve reliability, and turn messy operational problems into production-style systems.
Public portfolio includes deployed systems across Terraform, ECS Fargate, EKS/GitOps, Lambda/serverless, CloudOps governance, and business workflow automation.
Best fit
AWS Cloud Engineer · Cloud Infrastructure · Platform · DevOps
Proof
Public repos · live demos · tests · ADRs · teardown docs
Operating edge
Business workflows translated into reviewable cloud systems
Operating Model
Infrastructure is valuable when it improves the operation.
Cloud systems should be judged by how well they reduce operational drag, make change safer, and give teams better control.
Owner's Lens
I design infrastructure from the workflow outward.
What needs to be requested, approved, released, observed, audited, recovered, or handed off determines the architecture.
Reliability
Reviewability
Cost control
Auditability
Workflow speed
Maintainability
Operating constraints
Define what needs governance, rollback, observability, least-privilege access, cost controls, and auditability.
Production evidence
Leave behind infrastructure as code, policy checks, logs, runbooks, ADRs, teardown notes, and documented tradeoffs.
Result: systems that can be reviewed, operated, improved, and handed off without guesswork.
What This Produces
Cloud work tied to operating pressure.
Safer infrastructure changes
Terraform plan review, policy checks, blast-radius analysis, GitHub Actions, approval gates, and audit trails before apply.
Clearer operational control
CloudOps control planes, observability, audit logging, request replay, answer provenance, dashboards, and cost review.
Production-style AWS foundations
ECS Fargate, EKS/GitOps, Lambda/serverless, private networking, RDS, Cognito, WAF, CloudFront, and CloudWatch.
Automation for business handoffs
Lead intake, public-record research, CRM/API workflows, document processing, AI-assisted workflows, and structured data handoff.
Proof Systems
The projects are evidence of the operating model.
Each project shows how messy workflow pressure becomes architecture, controls, and reviewable operating evidence.
04 / Fargate Workflow API
Clearpath
A production-style ECS Fargate lead-intelligence API built around lead intake, source quality, county resolution, and acquisition workflows.
GrantStack
Event-driven incentive screening workflow with API Gateway, Lambda, SQS/DLQ, DynamoDB, S3 source catalog, scheduled refresh, CloudWatch/X-Ray, and Terraform.
GitHubPursuitDesk
GovCon capture workspace with SAM.gov opportunity scoring, async Bedrock proposal drafting, RDS/pgvector, and Terraform-backed workflow infrastructure.
GitHubBrokerOps + InvoiceBridge
Operational systems across ECS/RDS reconciliation, e-invoicing validation, audit paths, and structured handoff.
GitHub profilePhotoScribe, Super Transcriber, DocuFlow
Serverless media search, transcription workflows, OCR/document processing, and AI-assisted structured data workflows.
GitHub profile
Operator Lens
Before the cloud system, there is a messy workflow.
My engineering path started by building systems I needed to run real businesses: lead intake, public-record research, CRM/API workflows, client-facing websites, automation, and structured data handoff. That experience now informs how I design cloud systems: practical, reliable, cost-aware, and built around actual workflows.
01
Founder / Automation & Systems Lead at Clearpath Property Group / Boston Probate Solutions.
02
Owned web properties, DNS, SSL/TLS, Cloudflare, hosting, GitHub-based deployments, Supabase/Netlify, and WordPress administration.
03
Built Python ingestion workflows, CRM/API automation, AI prompt orchestration, and structured handoff paths for real operations.
Capabilities Underneath
The stack supports the operating model.
Tools and certifications matter here as validation, not as the brand. They are the materials used to build safer workflows and production-style systems.
Cloud and AWS
VPC, IAM, ECS Fargate, EKS, Lambda, API Gateway, Step Functions, S3, DynamoDB, RDS PostgreSQL, RDS Proxy, Bedrock, Textract, Cognito, CloudFront, WAF, ALB, ECR, SQS, EventBridge, CloudWatch, CloudTrail, Secrets Manager, SSM, Cost Explorer.
Infrastructure
Terraform, modular IaC, Terraform plan review, GitHub Actions, OIDC role assumption, Docker, Docker Compose, Cloudflare Pages, Checkov, TFLint, runbooks, ADRs.
Platform
Kubernetes, Amazon EKS, Helm, ArgoCD, IRSA, External Secrets, Prometheus, Grafana, GitOps patterns, ALB ingress.
Programming
Python, TypeScript, JavaScript, React, Next.js, FastAPI, PostgreSQL, SQL, Bash, REST APIs, data pipelines.
Security and Ops
Least-privilege IAM, private subnets, security groups, OPA/Rego, JWT/Cognito auth, presigned S3 URLs, WAF/rate limiting, secrets management, audit logging, OpenTelemetry, approval gates, CloudWatch alarms, cost controls.
Certifications: AWS Certified Solutions Architect Associate, AWS Certified Developer Associate, HashiCorp Terraform Associate.
Next Step
Need an AWS engineer who connects infrastructure to operational value?
I am open to cloud infrastructure, platform engineering, DevOps, and AWS engineering roles where ownership, reliability, automation, and business context matter.