EMR Message Exchange
Direct Secure Messaging integration — dev environment
Checking...
Contacting API health endpoint
What's live
- ✓AWS infrastructure — VPC, Lambda, Aurora Postgres, S3, EventBridge, DLQ
- ✓CI/CD pipeline — every push runs test → build → deploy → migrate → verify
- ✓Database schema deployed (5 tables)
- ✓Kno2 credentials loaded from Secrets Manager
- ✓Dispatcher tick running every minute
- ✓623 tests passing
Pending before real Kno2 traffic
- ◔Kno2 to allowlist our NAT egress IP
52.34.161.71 - ◔Kno2 to route inbound messages to our Direct address + webhook URL
- ◔Seed
SendDestinationrows (clinic → provider mappings)
Until Kno2 completes their side, outbound messages queue as PENDING,
retry with backoff, then land in the dead-letter queue with a CloudWatch alarm.
The app itself stays up.
Links
- →Health endpoint
- →GitLab repo
- →README
- →CloudWatch dashboard (requires AWS SSO)