Amazon CloudWatch
Complete Logs and Metrics nodes with safe batched telemetry
Amazon CloudWatch
AWSIKCloudWatch covers all 115 active CloudWatch Logs operations and all 50 CloudWatch Metrics operations in the pinned models. Three SDK-deprecated Logs operations are explicitly classified omissions. The portable telemetry role batches events and metrics, applies throttling limits, and flushes through module-owned clients.
Configure the log group, log stream, metric namespace, batch size, and whether PII-tagged events may leave the process. RecordEvent rejects invalid JSON and PII when policy disallows it. Structured payloads are recursively redacted for authorization, token, password, secret, credential, and signed-URL fields. Metrics enforce AWS name, value, and dimension count/length limits before they enter the queue.
Use low-cardinality dimensions such as build version, map, or region. Never use player ids, session ids, request ids, filenames, or free-form text as metric dimensions. Logs and metrics delivery is best effort and must not block gameplay or shutdown indefinitely.
Creating log groups, retention policies, destinations, subscriptions, metric alarms, dashboards, anomaly detectors, and streams belongs to a trusted deployment pipeline.