| Service Name: | CloudWatch |
| ARN Format: | arn:aws:logs:{region}:{account}:log-group:{name of group} |
| Style: | Async (Write) |
| Actions (required Permissions): |
logs:CreateLogStreamlogs:PutLogEvents |
| Payload Format: | Text line per packet, or JSON RequestPacket per packet with coap, coap+ and syslog formatters |
Proxylity's integration with CloudWatch Logs writes packet data arriving at your listener to a log group of your choice. Writing packets to logs is a natural fit for protocols where the packet data is encoded as a string (SYSLOG, for example). This type of destination is particularly helpful for archiving and forensic debugging activities.
Things to know about using CloudWatch Logs destinations:
utf8):
utf8, ascii, base64 or hex, each event is a
text line: a bracketed prefix with the sender address and port, the listener domain and port, and
the ingress region, followed by the formatted payload, for example
[203.0.113.10:51514 abc123:2514 us-west-2] <34>1 2026-11-03T22:14:15Z host app - - - message.coap, coap+ or syslog, each event is the
request packet as a single line of JSON with no prefix
(Tag, ReceivedAt, IngressRegion, Remote,
Local, Inner for decapsulated WireGuard traffic, Formatter
and the decoded Data object). CloudWatch treats these as
structured events, so Logs Insights queries, metric filters and subscription filters can match
on fields such as Data.severity.See CloudWatch Logs destinations in action in our SYSLOG example, which streams system log messages directly to CloudWatch Logs.
This type of destination isn't appropriate for protocols with arbitrary binary payloads (not strings).