Product-minded engineering / Atlanta

AI Applications & Cloud Engineer

Cloud systems people can understand, operate, and trust.

I turn business requirements into AI-assisted applications and cloud systems that teams can test, deploy, and operate—with clear data contracts, human decision boundaries, and explicit recovery paths.

The work starts with real operating needs and ends with systems another team can understand, operate, and own.

  • AI review
  • Web & native
  • AWS
  • Terraform
  • CI/CD
  • ECS & Serverless
  • DevSecOps
  • Observability

01 / SELECTED CLOUD SYSTEMS

Selected systems.

Independent projects. Each case study shows the architecture, key decisions, tradeoffs, and implementation behind the system.

  1. ShiftClarity

    A contract-to-invoice review workspace for healthcare staffing teams. It traces potential billing differences to approved terms and source records, preserves review decisions, and keeps unsupported work visible without inventing a financial answer.

    Independent synthetic AWS pilot · fictional records · assigned-account workspace

    Explore the case study

    System architecture ShiftClarity

    Inspect diagram
    ShiftClarity synthetic pilot: Cloudflare Pages proxy, API Gateway, FastAPI web Lambda and shared TypeScript calculation engine, Cognito MFA, private S3, SQS FIFO worker, and Neon PostgreSQL with transactional publication

    From approved work and dated terms to evidence-backed review. Deployed synthetic pilot / fictional records only; the standalone demo is a separate memory-only mode.

    Entry
    Identity is not permissionCognito MFA identifies a person; server-side memberships govern the persistent workspace.
    Processing
    One calculation contractReact and FastAPI share the exact-decimal engine. Private imports feed Lambda/SQS jobs.
    Data ownership
    Sources stay with the decisionNeon transactions preserve revisions, rules, immutable runs and audit. S3 retains private originals.
    Recovery
    Publish once, recover explicitlyJob claims, lease fencing, retries and a matched restore rehearsal support the synthetic workflow—not a production RPO/RTO.

    System review / ShiftClarity

    Inspect the architecture.

    Zoom for service labels. Scroll or swipe to explore the diagram.

    ShiftClarity synthetic pilot: Cloudflare Pages proxy, API Gateway, FastAPI web Lambda and shared TypeScript calculation engine, Cognito MFA, private S3, SQS FIFO worker, and Neon PostgreSQL with transactional publication
  2. InspectIQ

    A production-shaped platform for wholesale, auction, fleet, and offsite inspection teams. It connects guided photo capture, AI-assisted review, human-confirmed damage, grading, and buyer-ready condition reporting.

    Live AWS-backed application · session-only public walkthrough

    Explore the case study

    System architecture InspectIQ

    Inspect diagram
    InspectIQ architecture showing web and mobile clients, Cognito, API Gateway, Lambda, Neon Postgres, private S3, SQS and DLQ, Bedrock, EventBridge, a Python projector, DynamoDB, CloudWatch, X-Ray, SNS, Terraform, and GitHub Actions

    From inspection photos to reviewed condition reports.

    Entry
    Capture & identityWeb and mobile clients. Cognito JWT/RBAC is enforced by the application.
    Processing
    Queued image analysisPrivate S3 → SQS → Lambda → Bedrock. Human review remains authoritative.
    Data ownership
    Postgres is the recordNeon owns business facts; DynamoDB holds operational projections and idempotency state.
    Recovery
    Failed work stays visibleDLQs, replay controls, CloudWatch and X-Ray support investigation and recovery.

    System review / InspectIQ

    Inspect the architecture.

    Zoom for service labels. Scroll or swipe to explore the diagram.

    InspectIQ architecture showing web and mobile clients, Cognito, API Gateway, Lambda, Neon Postgres, private S3, SQS and DLQ, Bedrock, EventBridge, a Python projector, DynamoDB, CloudWatch, X-Ray, SNS, Terraform, and GitHub Actions
  3. TerraGate

    An evidence-first Terraform review workspace. Inspect plan changes, understand deterministic findings, and record scoped human decisions against the exact review snapshot—without giving the public demo permission to deploy infrastructure.

    Live constrained demo · deterministic checks · external writes mocked

    Explore the case study

    System architecture TerraGate

    Inspect diagram
    TerraGate deployed request flow: Cloudflare Workers and OpenNext to API Gateway, Python Lambda outside a VPC, and Neon Postgres over TLS. Plan files use ephemeral Lambda storage; GitHub writes are mocked and Terraform execution is disabled.

    From Terraform plans to evidence-linked decisions. The deployed path is Cloudflare Workers → API Gateway → Lambda outside a VPC → Neon. Plan files remain ephemeral; GitHub writes are mocked and Terraform execution is disabled. The RDS/private-VPC alternative is not shown as live infrastructure.

    Entry
    A bounded review workspaceCloudflare Workers serves the UI. The public demo uses shared dev identities.
    Processing
    Deterministic checksAPI Gateway → Python Lambda. Encoded Python rules produce the findings.
    Data ownership
    Evidence-linked decisionsNeon retains findings and audit history. Lambda /tmp plan files remain ephemeral.
    Recovery
    No deployment authorityExpired plan evidence is explicit. GitHub writes are mocked; Terraform execution is disabled.

    System review / TerraGate

    Inspect the architecture.

    Zoom for service labels. Scroll or swipe to explore the diagram.

    TerraGate deployed request flow: Cloudflare Workers and OpenNext to API Gateway, Python Lambda outside a VPC, and Neon Postgres over TLS. Plan files use ephemeral Lambda storage; GitHub writes are mocked and Terraform execution is disabled.
Portrait of Aiden Rhaa

Aiden Rhaa / independent builder and operator

02 / Operator profile

Built from the operator’s side of the handoff.

15+ years of delivery and 200+ client projects taught me to read a system as ownership, failure, recovery, communication, and cost—not just implementation.

I bring that perspective to application workflows, AI-assisted review, shared web/native contracts, and the AWS infrastructure beneath them. Terraform, serverless and container delivery, CI, observability, and security boundaries give the next engineer a concrete path to take over responsibly.

03 / Operating principles

Deploy. Defend. Observe. Recover. Hand Off.

Each principle points to an artifact, because an operating claim should be inspectable.

  1. 01

    Deploy

    Package the change, its infrastructure, and its validation path together.

    Review Clearpath Terraform
  2. 02

    Defend

    State the identity and write boundaries at the layer the evidence supports.

    Review InspectIQ security notes
  3. 03

    Observe

    Leave runtime proof, alarms, and qualifiers where the next operator can find them.

    Review InspectIQ runtime proof
  4. 04

    Recover

    Treat rollback, restore, and teardown as designed paths rather than improvised events.

    Review the Clearpath runbook
  5. 05

    Hand Off

    Pair architecture with limits and procedures so ownership can move without folklore.

    Review the InspectIQ runbook

04 / Supporting index

Supporting cloud systems.

  • AegisDesk

    AWS incident operations / evaluation deployment

    Team-scoped incident workspaces with evidence, runbooks, and action-specific human approvals.

    Evaluation deployment. Readiness and authenticated case listing verified; external integrations unconfigured.

    Evidence & boundaries

    Keep incident evidence, operator hypotheses, runbooks, and action approvals in one team-scoped case. Independent approval applies to an exact action; uncertain outcomes remain unresolved rather than triggering an automatic redispatch.

    October 10 AWS release: readiness and authenticated DynamoDB-backed case listing verified. Jira and CloudWatch integrations are unconfigured; hosted case writes and real ticket execution were not verified. Separately, draft PR #1 records a local Kubernetes evaluation: FastAPI + OPA in disposable Kind with Helm, readiness, PVC binding and upgrade CI. The SQLite chart rejects more than one API replica; this is not deployed EKS, high availability, or a production Kubernetes service.

    Incident workflowAWS release evidenceDraft Helm/Kind evaluation · local KubernetesLocal Kubernetes evidence ledgerEvaluation workspace
    AegisDesk controlled incident fixture showing an action workflow with approval and outcome boundaries
    Controlled local incident fixture / not a hosted incident or customer integration. The separate release record documents the verified AWS checks. Source record
  • Super Transcriber API

    AWS transcription API / independent release

    An AWS transcription API for applications that need private uploads, reliable background processing, and completion callbacks. Durable job admission, scoped API keys, measured usage, and signed webhook replay make processing explicit and recoverable.

    Independent AWS API release. Synthetic transcription and recovery checks recorded; no customer traffic or SLA claimed.

    Evidence & boundaries

    Durable job admission and an outbox connect private S3 uploads to SQS and Amazon Transcribe. Atomic usage settlement releases concurrency on completion; interrupted work has a reconciliation path. Scoped, revocable API keys, signed webhook retries and replay, an OpenAPI contract, and a TypeScript SDK make integration and ownership explicit. Release evidence records live upload-to-transcript checks, account isolation, and interrupted-job recovery.

    The documented hosted deployment has Stripe billing and Bedrock enrichment disabled. MP3/M4A are supported; source-URL ingestion and real-time streaming are not. Synthetic workflow checks are not accuracy, production-scale, customer-adoption, or service-level evidence.

    Architecture & recoveryOpenAPI contractTypeScript SDKRelease verificationProduct & API reference
  • CareFrame

    Hospital media workspace / powered by PhotoScribe AI

    A private workspace for hospital communications teams to find, upload, and review photos while keeping access permissions, consent status, and usage-rights context attached to each asset.

    Independent AWS-backed pilot with a fictional hospital and illustrative media.

    Evidence & boundaries

    Cognito staff roles, private S3 storage, Bedrock embeddings, S3 Vectors search, and DynamoDB asset policies govern the library and its short-lived image links. Approval, consent, rights, and role access remain separate controls. Recorded staff-workflow checks exercised sign-in, private upload and indexing, review-policy validation, and role-restricted access using disposable QA accounts.

    No hospital customer use, buyer acceptance, or regulatory certification is claimed. An approval label does not independently establish consent or usage rights. Invitation email delivery, enterprise SSO, and customer-approved retention and legal policies remain separate acceptance gates.

    C4 architectureStaff-workflow verificationPilot readiness & limitsOpen product · staff sign-in required
  • Market Scout Android

    Native market research / merged Android client

    Screen cities, ZIP codes, and counties before deeper property research. Saved lists, notes, favorites, and two- or three-market comparisons stay on the device; downloaded market snapshots support offline research.

    Android 1.1.0 source merged into master on October 13. CI builds a debug APK; no Google Play release is claimed.

    Evidence & boundaries

    Native Java views and the web client share a versioned public JSON contract rather than a shared UI or a paid backend. Frozen scan inputs and cancelable requests prevent stale callbacks from replacing new research. Private device storage preserves lists and drafts; atomic, snapshot-matched caching keeps offline readings explicit. The merge-commit Android CI passed JVM fixture tests, lint/build, and five API 35 emulator cases covering persistence and activity recreation.

    Offline lookup requires previously downloaded indexes and relevant shards; cached readings are labeled. Lists and notes are not synchronized across devices. Source freshness follows the generated Redfin snapshot; optional Census income uses the 2022 ACS estimate. Physical-device large-text/TalkBack qualification and Google Play distribution are not established by emulator CI.

    Android data contract & limitsMerged Android workPassing merge-commit CI & debug APKOpen web companion
    Market Scout native Android comparison screen with market metrics and saved-research controls
    Repository Android capture / merged client. Emulator checks are separate from physical-device qualification. Source record
  • Clearpath

    ECS Fargate API / retained validation

    A lead-intelligence API with container delivery, Terraform infrastructure, validation, observability, and an explicit teardown path.

    Independent reference system. Short-lived AWS validation; torn down after validation. No live demo.

    Evidence & boundaries

    FastAPI, PostgreSQL and RDS Proxy were exercised together on AWS Fargate. The retained case study explains the startup failure and correction, security boundaries, API checks, and operator handoff.

    Retained point-in-time evidence, not a continuing service or long-term availability claim. GHL-compatible intake is not a verified GHL integration; the cost model is an estimate, not billing evidence.

    Read the retained Clearpath case studyRetained validation evidence
  • Pulpit / Serverless

    AWS bilingual retrieval / deployed migration

    Cited Korean-English archive search, with S3 Vectors retrieval and versioned snapshots designed for rollback.

    Deployed migration. Local ingestion; recorded smoke checks are not a relevance or performance benchmark.

    Evidence & boundaries

    Search a Korean-English sermon archive with cited answers. S3 Vectors and sharded lexical retrieval keep embeddings out of query-Lambda memory; versioned snapshots publish the manifest last and preserve a rollback path. The October 7 migration retained 360 sermons and 8,191 chunks at that checkpoint.

    Individual API smoke observations, not a relevance or performance benchmark. Ingestion runs locally because the caption path is blocked from AWS IPs; cache-only polling is timeout recovery, not a durable job system. Snapshot cleanup remains manual.

    Migration & recoveryArchitectureOpen app · sign-in required
    Pulpit serverless query and publication paths: Cognito, API Gateway, Lambda, S3 Vectors, lexical snapshots in S3, DynamoDB cache and audit, Bedrock, and a local ingestion runner
    Query and snapshot-publication paths / based on the October 7 architecture and migration record. Local ingestion is distinct from the legacy AWS ingestion path. Source record
  • Pulpit V2

    Validated EKS and GitOps platform

    A migration path from serverless retrieval to Kubernetes with observability, secrets discipline, and teardown artifacts.

    Repository
  • DocuFlow OCR

    Document-processing workflow

    Presigned intake, orchestration, OCR, parsing and scoring, human review, dead-letter handling, and alarms.

    Repository
  • WorshipCue

    Offline-first iPad workflow / independent development

    Offline charts, handwritten notes, and team rehearsal workflows built around exact chart versions.

    Independent development. Latest work partly local; no App Store release or qualified multi-iPad pilot.

    Evidence & boundaries

    A music stand for rehearsal: keep charts available offline, preserve handwritten notes, and coordinate exact chart versions, team access, cues, and chat through a cloud workspace. Native usability, permissions, and recovery are designed around the same operating workflow.

    Latest native/backend work remains partly local; published source checkpoints are earlier builds. Selected AWS and managed-session checks are recorded, but there is no App Store release or fully qualified multi-iPad rehearsal pilot. Capacity and final gesture qualification remain open.

    Engineering decisionsPublication & verification

05 / Experience

Professional experience

  1. Founder / Automation & Systems Lead

    Clearpath Property Group / Boston Probate Solutions

    Dec 2016—Present / Atlanta Metropolitan Area

    Owned lead intake, public-record research, market data, CRM integration, seller communication, and automation; translated those operating requirements into webhook, API, and cloud workflow artifacts.

  2. Creative Director / Operations

    Aiden Rhaa Photography / Visual Impact Studios

    Oct 2010—Present / Atlanta Metropolitan Area

    Delivered 200+ client projects while coordinating contractors, vendors, budgets, timelines, technical execution, web properties, deployment workflows, and high-touch client communication.

  3. Multimedia Producer / Technical Workflow Lead

    ProMedia Productions

    May 2009—Dec 2016 / Boston, Massachusetts

    Managed end-to-end audio and video delivery, automated media-file handling, and designed recording workflows for small-business, corporate, and education clients.

06 / Contact

Let’s talk about your engineering team.

AI-assisted applications, business workflows, and the cloud infrastructure that makes them operable.