The Trinity Beast – Command Center Guide

1. Overview

The Trinity Beast Command Center (TBCC) is a unified operations dashboard that brings together all administrative functions for The Trinity Beast Infrastructure into a single browser-based interface. Rather than switching between multiple AWS Console tabs, admin pages, and terminal windows, the TBCC provides everything you need in one place.

The console is designed as a widget-based dashboard modeled after the AWS Console experience, with a dark theme and card-based layout that organizes operational tools by function. Key capabilities include:

• Widget-based dashboard — Seven functional widgets organized in a responsive grid, each covering a distinct area of the infrastructure (Newsletter, Support, Email, CloudWatch, Stripe, Testing, AWS Operations).
• Real-time terminal with WebSocket relay — Execute AWS CLI commands, cURL requests, and shell commands directly from the browser. A lightweight Python WebSocket server running on Cory Dean Kalani's MacBook Neo bridges the browser to the local shell.
• Direct links to all admin consoles — One-click access to the Newsletter Admin Console, Support Admin Console, and Email Admin Console.
• Pre-built operational commands — Ready-to-run commands for ECS container management, Aurora database status, ElastiCache health, Lambda monitoring, S3 file management, and CloudFront invalidation.
• CloudWatch dashboard integration — Direct links to application dashboards, log groups, and alarm configurations in AWS CloudWatch.
• API testing tools — Pre-configured cURL commands for health checks, price queries, admin config, support stats, newsletter templates, email senders, and more — with one-click Run and Copy buttons.

2. Getting Started

2.1 Prerequisites

Before using the TBCC, ensure the following are in place on your Neo machine:

• macOS with Python 3 installed (ships with macOS or install via Homebrew).
• AWS CLI configured with credentials for account 211998422884 (region us-east-2). Run aws sts get-caller-identity to verify.
• websockets Python package — The terminal relay script auto-installs this on first run if it is not already present.
• The trinity-beast-lpo-server/scripts directory on your PATH so that tbccstart and tbccstop can be run from any terminal window.

2.2 Starting the Terminal Relay

The terminal relay is a lightweight Python WebSocket server that bridges the TBCC browser interface to your local shell. To start it, run tbccstart from any terminal window.

• It starts a WebSocket server on ws://127.0.0.1:9999 (localhost only — not network accessible).
• The process runs in the background. Logs are written to /tmp/tbcc-relay.log.
• The PID is stored in /tmp/tbcc-relay.pid for clean shutdown.
• The TBCC page auto-connects to the relay when opened in a browser.
• If the relay is already running, the script detects it and exits without starting a duplicate.

#!/bin/bash
# The Trinity Beast Command Center — Start Terminal Relay
# Run from anywhere: tbccstart

SCRIPT_DIR="$(cd "$(dirname "$(readlink -f "$0" 2>/dev/null || echo "$0")")" && pwd)"
RELAY="$SCRIPT_DIR/terminal-relay.py"

if ! [ -f "$RELAY" ]; then
  echo "❌ terminal-relay.py not found at $RELAY"
  exit 1
fi

# Check if already running
if pgrep -f "terminal-relay.py" > /dev/null 2>&1; then
  echo "⚡ Terminal Relay is already running (PID $(pgrep -f terminal-relay.py))"
  exit 0
fi

nohup python3 "$RELAY" > /tmp/tbcc-relay.log 2>&1 &
PID=$!
echo $PID > /tmp/tbcc-relay.pid
sleep 1

if kill -0 $PID 2>/dev/null; then
  echo "✅ Terminal Relay started (PID $PID)"
  echo "   Listening on ws://127.0.0.1:9999"
  echo "   Log: /tmp/tbcc-relay.log"
  echo "   Stop: tbccstop"
else
  echo "❌ Failed to start. Check /tmp/tbcc-relay.log"
  exit 1
fi

2.3 Stopping the Terminal Relay

To stop the terminal relay, run tbccstop from any terminal window. This kills the background relay process and cleans up the PID file.

#!/bin/bash
# The Trinity Beast Command Center — Stop Terminal Relay
# Run from anywhere: tbccstop

PIDS=$(pgrep -f "terminal-relay.py")

if [ -z "$PIDS" ]; then
  echo "⚡ Terminal Relay is not running."
  rm -f /tmp/tbcc-relay.pid
  exit 0
fi

kill $PIDS 2>/dev/null
rm -f /tmp/tbcc-relay.pid
echo "✅ Terminal Relay stopped (PID $PIDS)"

2.4 Accessing the Console

Once the terminal relay is running, open the TBCC in any browser:

https://cpmp-site.org/admin/trinity-beast-command-center.html

• The connection status indicator in the top-right corner of the navigation bar shows ● Online when the relay is connected.
• If the indicator shows ● Offline, ensure you have run tbccstart in your local terminal.
• The console works in Chrome, Firefox, Safari, and Edge. No browser extensions are required.

3. Console Layout

The TBCC is organized into distinct visual regions designed for efficient operations workflow:

• Top navigation bar — Contains the Trinity Beast branding, relay connection status indicator (green/red badge), and quick links to the AWS Console and the cpmp-site.org website.
• Widget grid — Seven functional widgets arranged in a responsive grid layout. On wide screens (1200px+), widgets display in 3 columns. On medium screens, 2 columns. On mobile, a single column. Each widget follows the AWS Console card design pattern: a colored icon in the header, a title, and a body containing service tiles or command lists.
• Terminal widget — A full-width panel at the bottom of the page providing an integrated terminal emulator with macOS-style chrome (red/yellow/green window dots), command input bar, and streaming output display.

The six widgets are:

1. Newsletter Administration — Orange envelope icon
2. Support Administration — Blue chat bubble icon
3. Email Administration — Purple open envelope icon
4. CloudWatch Monitoring — Cyan bar chart icon
5. Stripe Administration — Indigo Stripe "S" icon
6. Testing & cURL Commands — Green lab flask icon
7. AWS Operations — Rose server stack icon

TBCC Dashboard — Full Widget Grid

Below is a representative view of the TBCC dashboard showing all six widgets, the top navigation bar with relay status and Demo Key toggle, and the terminal panel at the bottom:

4. Newsletter Administration Widget

Icon: ✉ Orange envelope  |  Purpose: Manage newsletter creation, templates, subscribers, and sending.

The Newsletter Administration widget provides quick-access tiles to the Newsletter Admin Console and its key sections. Each tile links directly to the relevant tab so you can jump straight into the task at hand.

Service Tiles

Newsletter Admin Console — Archive Tab

The archive tab displays all sent and active newsletters with type badges, dates, and status indicators. Below is a representative view of the archive:

5. Support Administration Widget

Icon: 💬 Blue chat bubble  |  Purpose: Manage customer support tickets, respond to inquiries, and track resolution.

The Support Administration widget provides access to the full support ticket lifecycle — from customer submission through resolution and closure. It links to both the admin-facing console and the public-facing support page.

Service Tiles

Workflow Statuses

Support tickets progress through the following statuses as they move through the resolution workflow:

Categories

Tickets are classified into the following categories to help route and prioritize them:

• General Inquiry — General questions about the platform or services
• API/Technical Support — Issues with API keys, endpoints, integrations, or WebSocket feeds
• Billing/Subscription — Payment, invoices, subscription tier changes, receipts
• Bug Report — Something is broken or not working as expected
• Feature Request — Suggestions for new features or improvements
• Mission/Donations — Questions about the CPMP mission, donations, or field operations

Support Admin Dashboard

The dashboard provides an at-a-glance view of ticket volume and status distribution, along with a table of recent tickets.

Public Support Page

The public support page at cpmp-site.org/support.html allows customers to submit new tickets without needing an admin account. Below is a representative view of the submission form:

6. Email Administration Widget

Icon: 📨 Purple open envelope  |  Purpose: Compose and send emails via Amazon SES with templates, drafts, and configurable senders.

The Email Administration widget provides access to the Email Admin Console where you can compose emails using pre-built templates, manage drafts, and configure sender addresses. All emails are sent through Amazon SES with proper DKIM and SPF authentication.

Service Tiles

Configured Senders

The following sender identities are configured in Amazon SES for use with the Email Admin Console:

Email Admin Console — Compose Tab

The compose tab provides a rich email editor with template selection, sender configuration, recipient management, and a Quill.js rich text editor for the email body.

Email Translations Management

Newsletter welcome emails are language-aware. The email_translations table in Aurora stores all translatable text fields for each SES template. When a subscriber signs up, the server looks up their preferred language and passes the translated fields to SES. To update any translation, modify the row in the table — no code changes or redeployment required.

Viewing Translations

To view all translations for a template and language:

POST /admin/sql
{"query": "SELECT field_name, field_value FROM email_translations WHERE template_name = 'CPMPNewsletterWelcome' AND lang = 'de' ORDER BY field_name", "mode": "read"}

Updating a Translation

To update a single field (e.g., change the German subject line):

POST /admin/sql-batch
{"query": "UPDATE email_translations SET field_value = 'Willkommen beim CPMP-Newsletter' WHERE template_name = 'CPMPNewsletterWelcome' AND lang = 'de' AND field_name = 'heading'"}

Adding a New Language

To add a new language (e.g., Italian), insert all fields for each template:

POST /admin/sql-batch
{"query": "INSERT INTO email_translations (template_name, lang, field_name, field_value) VALUES ('CPMPNewsletterWelcome', 'it', 'subject', 'Benvenuto alla Newsletter CPMP'), ('CPMPNewsletterWelcome', 'it', 'heading', 'Benvenuto alla Newsletter CPMP'), ... ON CONFLICT (template_name, lang, field_name) DO UPDATE SET field_value = EXCLUDED.field_value;"}

7. CloudWatch Monitoring Widget

Icon: Cyan bar chart  |  Purpose: Direct links to AWS CloudWatch dashboards and monitoring resources.

The CloudWatch Monitoring widget provides one-click access to the key monitoring dashboards, log groups, and alarm configurations in AWS CloudWatch. These links open directly in the AWS Console for the us-east-2 region.

Service Tiles

8. Stripe Administration Widget

Icon: 💳 Indigo Stripe "S" logo  |  Purpose: Centralized access to all Stripe Dashboard functions for managing subscriptions, customers, payments, products, webhooks, and reporting.

Widget Sections

Subscriptions & Customers

Products & Revenue

Configuration & Webhooks

Reporting & Logs

9. Testing & cURL Commands Widget

Icon: Green lab flask  |  Purpose: Pre-built API test commands with one-click copy or execute functionality.

The Testing widget contains a library of ready-to-run cURL commands that cover the most common API testing and diagnostic scenarios. Each command has a Run ▶ button (executes in the terminal widget) and a Copy 📋 button (copies to clipboard for use in an external terminal).

Available Commands

Testing Widget with Terminal Output

When you click Run ▶ on a command, it executes through the WebSocket relay and the output streams into the terminal widget at the bottom of the page. Below is a representative view:

10. AWS Operations Widget

Icon: 🖥 Rose server stack  |  Purpose: Operational AWS CLI commands organized by service category for infrastructure management.

The AWS Operations widget is the most command-dense widget on the dashboard. It organizes pre-built AWS CLI commands into logical service categories, each with Run and Copy buttons. Commands cover the full operational surface of The Trinity Beast Infrastructure.

ECS Exec Tunnels

ECS Exec tunnels provide interactive shell access to running containers. These are the most frequently used operational commands.

ECS Management

Database

Lambda

ECR

S3 & CloudFront

Logs

EventBridge

Sync Job

The nightly sync job runs at 1:00 AM EST via EventBridge → ECS Fargate. It syncs Aurora → ElastiCache (price logs, usage logs, API keys, application parameters) and prunes old data. Check this first thing each day after the health check.

Secrets

Kiro CLI

Kiro CLI (v2.0.0) provides an AI-powered terminal chat session directly from the TBCC. Use it for natural language AWS operations, code generation, and troubleshooting.

Database Tools

Database administration tools for connecting to Aurora PostgreSQL via port forwarding. Use with pgAdmin, DBeaver, or psql on your Neo machine.

AWS Operations Widget — Dashboard View

Below is a representative view of the AWS Operations widget as it appears on the TBCC dashboard, showing the command sections with Run and Copy buttons:

11. Terminal Widget

Icon: 💻 Cyan terminal prompt  |  Purpose: Built-in terminal emulator connected to your local MacBook via WebSocket relay.

The terminal widget is a full-width panel at the bottom of the TBCC dashboard that provides a browser-based terminal experience. It connects to Cory Dean Kalani's MacBook Neo through the WebSocket relay server (terminal-relay.py) and can execute any command the local shell can run.

Features

• macOS-style terminal chrome — Red, yellow, and green window dots for a familiar look and feel.
• One-click execution — Click Run ▶ on any command in the Testing or AWS Operations widgets and the output streams into the terminal in real time.
• Direct command input — Type commands directly into the input bar at the bottom of the terminal panel and press Enter to execute.
• Clear — Wipe all terminal output to start fresh.
• Kill — Send a Ctrl+C equivalent to terminate a running command.
• Reconnect — Re-establish the WebSocket connection if it drops.
• Connection status — Shown both in the top navigation bar and as a badge on the terminal panel itself.

Architecture

The terminal relay uses a simple architecture with no external dependencies beyond the websockets Python package:

Browser (TBCC) ←→ WebSocket ←→ terminal-relay.py (localhost:9999) ←→ bash shell

The relay listens only on 127.0.0.1 (localhost), so it is not accessible from other machines on the network. Each command sent from the browser spawns a subprocess on the Neo machine, and stdout/stderr are streamed back to the browser over the WebSocket connection.

Terminal in Action

Below is a representative view of the terminal widget showing output from a health check and a price query:

12. Partner Management Widget

Icon: 👥 Teal people silhouettes  |  Purpose: Onboard, manage, and monitor AWS partners connected via PrivateLink (TCP) or VPC Peering (UDP).

The Partner Management widget organises its functionality across four tabs: Partners (view all connected partners), Pending Approvals (accept or reject incoming connection requests), Security Groups (manage UDP access CIDRs), and Onboard Partner (a step-by-step wizard that generates the exact CLI commands for both sides of the connection).

Tab Descriptions

• Partners — Lists all connected partners with their connection type (PrivateLink or VPC Peering), status, VPC CIDR, and onboarding date. Click any partner to view connection details and health metrics.
• Pending Approvals — Shows incoming PrivateLink endpoint requests and VPC peering requests awaiting acceptance. One-click approve or reject with confirmation.
• Security Groups — Manage the ECS security group rules that grant UDP access to peering partners. Add or remove partner CIDRs without leaving the dashboard.
• Onboard Partner — A three-step wizard (shown above) that collects the connection type, partner details, and generates the exact AWS CLI commands for both the Trinity Beast side and the partner side.

13. Exchange Manager Widget

Icon: 🔄 Emerald exchange arrows  |  Purpose: Manage all 6 real-time WebSocket exchange feeds and their 150 asset mappings from a single dashboard widget.

The Exchange Manager widget is the operational control panel for The Trinity Beast's table-driven exchange architecture. It provides full visibility into every WebSocket feed, every asset-to-symbol mapping, and every runtime metric — organized across three tabs.

Tab 1 — Exchange Feeds

A live table showing all 6 configured exchanges with their connection status, WebSocket endpoint, source tag, and asset count. Each row includes an Enable/Disable toggle that calls POST /admin/exchange-feeds/toggle — no deploy required.

Tab 2 — Asset Mappings

A filterable table of all 150 asset-to-symbol mappings across all exchanges. Filter by exchange name to see just one exchange's assets. Each row shows the normalized asset name (BTC), the exchange-specific symbol (BTC-USD, btcusd, BTC/USD, etc.), and an enabled flag.

Asset mappings are managed via POST /admin/exchange-assets/save (batch upsert) and DELETE /admin/exchange-assets (single or bulk delete). The public GET /exchanges endpoint reads from these same tables to power the demo dropdown on the subscription page.

Tab 3 — Runtime Metrics

18 color-coded metric cards pulled from GET /admin/stress-stats, showing the real-time state of the container that handled the request. Metrics are grouped into categories:

• Throughput — TCP requests, UDP requests, LRS requests (total counts since last reset)
• Cache Performance — sync.Map hits, ElastiCache hits, cache misses, hit percentages
• UDP Health — Packets received, dropped, sent, drop percentage
• Background Pool — Work submitted, dropped, completed, drop percentage
• Batch Pipeline — Rows queued, flushes, flush errors
• Database — Open connections, in-use connections, wait count

Cards turn green for healthy values, amber for warning thresholds, and red for critical values (e.g., UDP drop % > 1%, 5xx errors > 0, batch flush errors > 0).

API Endpoints Used

14. Cluster Health Widget

Icon: 🏥 Red heart pulse  |  Purpose: Real-time health monitoring of all 3 ECS containers via ElastiCache-based cluster-wide aggregation.

The Cluster Health widget is the first widget on the TBCC dashboard — a full-width panel that shows the operational state of all 3 containers (BeastMain, BeastMirror, BeastLRS) at a glance. Unlike a simple port health check, this widget shows actual runtime metrics from inside each container.

Architecture — ElastiCache-Based, Not ALB Polling

Each container runs a background goroutine (StartMetricsPublisher()) that publishes its 24-counter metrics snapshot to ElastiCache every 3 seconds. The widget calls GET /admin/cluster-stats, which reads all 3 snapshots in a single ElastiCache pipeline call — one round-trip, sub-millisecond, guaranteed all 3 containers.

ElastiCache Keys

If a container hasn't published in 30 seconds, its key expires and the widget shows it as missing — an immediate signal that something is wrong.

Widget Layout — 3 Side-by-Side Cards

The widget displays 3 cards in a horizontal row, one per container. Each card shows:

Header Badge & Refresh

The widget header shows a badge indicating how many nodes are reporting — 3/3 Nodes in green when all containers are healthy, or 2/3 Nodes in red if any container is missing.

The widget auto-loads on page open and includes a "Check All Nodes" refresh button. The dashboard currently refreshes on a 30-second timer.

CloudWatch Integration

Six key runtime metrics from the cluster stats are also published to CloudWatch for dashboard and alarm visibility:

• UDPDropPct — UDP packet drop percentage
• BgDropPct — Background work drop percentage
• DBInUseConns — Database connections currently in use
• DBWaitCount — Database connection pool wait count
• BatchFlushErrors — Batch pipeline flush error count
• SyncMapHitPct — sync.Map cache hit percentage

15. Child Pages

The TBCC links to four child pages that provide full-featured admin consoles and the public-facing support interface. Each child page is a standalone HTML application that communicates with the Trinity Beast API backend.

15.1 Newsletter Admin Console

URL: cpmp-site.org/admin/newsletteradmin.html

The Newsletter Admin Console is a full-featured newsletter management application with four main sections accessible via a sidebar navigation:

• Archive — Browse all sent and active newsletters. Each entry shows the title, date, type badge (CPMP or Listener), and status. Click any newsletter to view its full content.
• Compose — Create new newsletters using a template selector, type pills (CPMP/Listener), and a Quill.js rich text editor. Save as draft or send immediately to the selected subscriber list.
• Templates — Create, edit, and delete reusable newsletter templates. Templates define the layout, header, footer, and default content blocks that can be customized when composing.
• Subscribers — View subscriber statistics (total count, by type) and a filterable list of all subscribers with their email addresses and subscription type.

Compose Tab with Template Cards

The compose tab displays available templates as selectable cards. Clicking a template pre-fills the editor with the template's layout and default content.

15.2 Support Admin Console

URL: cpmp-site.org/admin/supportadmin.html

The Support Admin Console provides a complete ticket management system with three main sections:

• Dashboard — Stats cards showing ticket counts by status, plus a table of recent tickets sorted by date.
• Tickets — A filter bar (by status, category, date range) and a full ticket table. Click any ticket to expand a detail panel showing the original message, admin replies, internal notes, and status history.
• Settings — Reference tables for status definitions and category descriptions.

Ticket Detail Panel

Expanding a ticket reveals the full conversation thread, including the original customer message, admin replies, and internal notes (visible only to admins).

15.3 Email Admin Console

URL: cpmp-site.org/admin/emailadmin.html

The Email Admin Console provides a complete email management system with four main sections accessible via sidebar navigation:

• Templates — Create, read, update, and delete email templates. Each template has a topic, subject line, and HTML body content. Templates can be selected when composing to pre-fill the email fields.
• Compose — Build and send emails using a template dropdown, sender dropdown, recipient fields (To, CC, BCC), and a Quill.js rich text editor for the email body. Emails are sent through Amazon SES.
• Drafts — Resume previously saved email drafts. Drafts can be filtered by status (draft, sent, failed) and sorted by date. Click any draft to reload it into the compose editor.
• Senders — Manage from-addresses with display names and reply-to configurations. Each sender identity must be verified in Amazon SES before it can be used.

15.4 Public Support Page

URL: cpmp-site.org/support.html

The public support page is the customer-facing interface for the support system. It provides three main functions:

• Submit a ticket — A form with fields for name, email, category (dropdown), subject, and message. On submission, the ticket is created in the backend and the customer receives a confirmation with their ticket number.
• Ticket lookup by email — Customers can enter their email address to see all tickets they have submitted, along with current status and any admin replies.
• Ticket detail view — View a specific ticket's full conversation thread, including the original message and all replies. Customers can add follow-up messages from this view.

The page supports permanent links for direct access:

• support.html?email=bugs.bunny@acme.com — Opens the ticket list for a specific email address.
• support.html?ticket=CPMP-20260417-a3f1 — Opens a specific ticket's detail view directly.

16. API Endpoint Reference & Authentication

All admin API endpoints are protected by the X-Admin-Key header. Public endpoints (health checks, price queries, customer-facing support) require no authentication. The admin key is stored in the application_parameters table and can be changed at any time without redeploying.

Authentication

curl -H "X-Admin-Key: YOUR_ADMIN_KEY" https://api.cpmp-site.org/admin/config

Public Endpoints (No Authentication Required)

These endpoints are accessible without any API key or admin key. They serve customer-facing functionality and health monitoring.

Admin Endpoints — Core Administration

All endpoints below require the X-Admin-Key header.

Admin Endpoints — Newsletter Management

Admin Endpoints — Email Management

Admin Endpoints — Support Ticket Management

LRS Report Endpoints (on lrs.cpmp-site.org)

These endpoints are on the LRS server (lrs.cpmp-site.org) and require a subscriber API key via the Authorization: Bearer header — not the admin key.

17. Troubleshooting

Common issues and their solutions when working with the TBCC: