The Trinity Beast — AWS Partner Onboarding Guide

1 Share the service name with the partner:

com.amazonaws.vpce.us-east-2.vpce-svc-0147410454a727b3f

2 Wait for their endpoint request — it will appear in the VPC console under Endpoint Services → Endpoint Connections.

3 Accept the connection request:

aws ec2 accept-vpc-endpoint-connections \
  --service-id vpce-svc-0147410454a727b3f \
  --vpc-endpoint-ids vpce-XXXXXXXXXXXX \
  --region us-east-2

That's it. No security group changes, no route table changes, no CIDR coordination.

1 Create a VPC Interface Endpoint in their VPC:

aws ec2 create-vpc-endpoint \
  --vpc-id vpc-THEIR_VPC_ID \
  --service-name com.amazonaws.vpce.us-east-2.vpce-svc-0147410454a727b3f \
  --vpc-endpoint-type Interface \
  --subnet-ids subnet-THEIR_SUBNET \
  --security-group-ids sg-THEIR_SG \
  --region us-east-2

2 Wait for CPMP to accept the connection.

3 Use the endpoint DNS to connect:

# LPO price query via PrivateLink (request/response)
curl http://vpce-XXXX.vpce-svc-0147410454a727b3f.us-east-2.vpce.amazonaws.com:8080/price?asset=BTC&api_key=YOUR_KEY

# LRS report via PrivateLink
curl http://vpce-XXXX.vpce-svc-0147410454a727b3f.us-east-2.vpce.amazonaws.com:9090/reports/usage?api_key=YOUR_KEY

# Real-Time WebSocket Feed (persistent connection — prices pushed as they arrive)
wscat -c "ws://vpce-XXXX.vpce-svc-0147410454a727b3f.us-east-2.vpce.amazonaws.com:8080/ws/prices?api_key=YOUR_KEY"
# Then subscribe: {"subscribe": ["BTC","ETH","SOL"]}
# Prices flow continuously — no polling required

Partners can open a persistent WebSocket connection at /ws/prices?api_key=KEY and receive real-time price updates pushed from the same exchange feeds that power the entire system. No polling, no intervals — prices arrive the instant they're received from the 6 exchanges.

Available assets: GET /ws/assets — returns all 150 prewarmed assets across 6 exchanges. No auth required (informational endpoint).

1 Accept the peering request (partner initiates):

aws ec2 accept-vpc-peering-connection \
  --vpc-peering-connection-id pcx-XXXXXXXXXXXX \
  --region us-east-2

2 Add route to your public route table for the partner's CIDR:

aws ec2 create-route \
  --route-table-id rtb-0b16435cb481bf79d \
  --destination-cidr-block PARTNER_CIDR \
  --vpc-peering-connection-id pcx-XXXXXXXXXXXX \
  --region us-east-2

3 Add security group rule to allow UDP from the partner's CIDR:

# Allow UDP 2679 (LPO) from partner
aws ec2 authorize-security-group-ingress \
  --group-id sg-050b617f93b2388f6 \
  --protocol udp --port 2679 \
  --cidr PARTNER_CIDR \
  --region us-east-2

# Allow UDP 2680 (LRS) from partner
aws ec2 authorize-security-group-ingress \
  --group-id sg-050b617f93b2388f6 \
  --protocol udp --port 2680 \
  --cidr PARTNER_CIDR \
  --region us-east-2

4 Provide the NLB private IP to the partner (static per AZ — does not change on deployments).

1 Create VPC Peering request to your VPC:

aws ec2 create-vpc-peering-connection \
  --vpc-id vpc-THEIR_VPC_ID \
  --peer-owner-id 211998422884 \
  --peer-vpc-id vpc-03deaddb7083cd59c \
  --peer-region us-east-2 \
  --region THEIR_REGION

2 Wait for CPMP to accept.

3 Add route for The Trinity Beast VPC:

aws ec2 create-route \
  --route-table-id rtb-THEIR_RT \
  --destination-cidr-block 10.0.0.0/16 \
  --vpc-peering-connection-id pcx-XXXXXXXXXXXX \
  --region THEIR_REGION

4 Send UDP queries to the NLB private IP (provided by CPMP):

# UDP LPO price query (Python example)
import socket, json
sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
payload = json.dumps({"asset": "BTC", "api_key": "YOUR_KEY"})
sock.sendto(payload.encode(), ("NLB_PRIVATE_IP", 2679))
data, _ = sock.recvfrom(4096)
response = json.loads(data)
print(json.dumps(response, indent=2))

# Response — Unified Messaging Envelope (same 12-field structure as TCP):
# {
#   "status": "✅ [LPO] [us-east-2] [BeastMain] [/price] [200]",
#   "status_code": 200,
#   "endpoint": "/price",
#   "cluster_node": "BeastMain",
#   "region": "us-east-2",
#   "language": "en",
#   "api_key_id": "YOUR_KEY",
#   "ip_address": "10.0.1.50",
#   "agent_profile_arn": "arn:tbi:us-east-2:211998422884:agent-profile/tbi/v1",
#   "timestamp": "2026-05-29T22:00:00Z",
#   "data": {
#     "assets": [{
#       "asset": "BTC",
#       "price": 97432.384729501,
#       "exchange": "coinbase-ws",
#       "cached": true,
#       "cache_age_seconds": 0.847,
#       "timestamp": 1748548800,
#       "readable_timestamp": "2026-05-29T22:00:00Z",
#       "latency_ms": 0
#     }],
#     "failed": [],
#     "duration_ms": 1,
#     "monthly_usage": 0,
#     "monthly_limit": 0,
#     "usage_pct": 0.0,
#     "usage_warning": ""
#   },
#   "error": ""
# }

The NLB IP is static — it survives container deployments, scaling events, and AZ failovers. No reconnection logic needed.