Observability as an integration path
Local packet capture is not always possible for remote devices, global endpoints, or encrypted transport. This architecture fans packets into SQS, processes them with Lambda, and publishes structured events to browser subscribers through AppSync Events.
UDP or WireGuard → Proxylity listener → primary destination
Same listener → SQS → Lambda → AppSync Events → browsers
Transport flexibility and protocol awareness
Plain UDP and WireGuard are ingress transports. After WireGuard traffic is decapsulated, the capture processor can inspect application protocols including CoAP, DHCP, SSDP, syslog, and RADIUS. Keeping those layers distinct makes the same observability pipeline useful across several architectures.
Nondisruptive fan-out
Add visibility as a secondary destination without inserting an observer into the primary processing path.
No persistent capture store
SQS provides transient buffering; packets flow directly to connected browser subscribers.
Multiple subscribers
AppSync Events fans the same live stream out to any number of browser tabs.
Self-contained deployment
The UI is served by Lambda, so there is no separate frontend hosting stack to operate.
Deploy and observe
The example supports plain UDP, optional WireGuard ingress, and includes a deployment walkthrough. Use it for ad-hoc debugging, protocol validation, or as a pattern for adding live observability to another listener.
View source and deployment steps →
Watch the deployment walkthrough →