Skip to content
JB360 Docs

AWS — Deployed Infrastructure

Live verification of account 660537473428 (us-east-1), performed 2026-07-07 with read-only AWS CLI calls (list/get/describe only; nothing modified) plus a read-only inspection of the production database (information_schema and routine definitions only). Fills the runtime gaps the source-only docs couldn’t answer. No secret values appear in these pages.

Contents

Section titled “Contents”
PageCovers
lambda-inventory.mdAll deployed functions, the extraction Lambdas’ real config, template-vs-deployed drift
schedules-and-queues.mdEvery EventBridge schedule (the sync heartbeat) and SQS queue/DLQ wiring
apis-auth-hosting.mdAPI Gateways, live authorizer state, Cognito pools, CloudFront/S3 hosting, RDS instances/proxies, VPC/network layout
database.mdThe jbwst schema: all tables with row counts, views, and every stored procedure’s logic (matching engine, agreement factory, claims detection)
deployment-history.mdOrigin of the system (Jan 2024 Maktix handover) and the manual deploy procedure

Headline Findings

Section titled “Headline Findings”
  1. CloudFormation is 2 years stale. Stack jbw-prod-api last updated 2024-05-06, jbw-stage-api 2024-04-27 — yet many Lambdas show 2025–2026 modification dates. Everything since May 2024 was deployed outside SAM. The repo’s template.yaml describes May 2024, not today.
  2. A full dev/stage environment exists (99 dev_* functions, own API Gateway, Cognito pool, queue, jbw360-stage.jbwarranties.com) even though samconfig.toml only defines prod.
  3. Cognito auth IS currently attached to both portal APIs — the template’s “deploys with no authorizer” risk is real at deploy time but remediated in the live account.
  4. ~40 prod Lambdas are not in the template; about a dozen have no source anywhere in the repo.
  5. A second, newer API exists: JB360IntegrationAPI (created 2026-01-13) fronting the jb360dealer Java Lambdas — none of it in this repo.

Follow-ups Worth Considering

Section titled “Follow-ups Worth Considering”
  • Decide the source of truth: re-adopt SAM (import drift, fix the template’s indentation bug) or officially treat the console as truth.
  • Dev and Workiz queues have no DLQ — failures are silently dropped after retries.
  • Duplicate daily schedules on prod_getTenantInfo and prod_jbwequipmentsyncstoredpro.
  • Recover/track source for the ~12 repo-less prod functions (incl. the jb360dealer API).