Amazon ElastiCache Logs

Ship Amazon ElastiCache slow logs and engine logs for Valkey and Redis OSS clusters to Bronto to troubleshoot latency, evictions, and command usage.

Amazon ElastiCache for Valkey and Redis OSS can publish two log streams: the slow log (commands that exceeded a configured execution threshold) and the engine log (a curated, redacted subset of server events such as replication, snapshots, and cluster health). Both can be delivered to CloudWatch Log Groups or to Amazon Data Firehose. ElastiCache for Memcached doesn’t emit these log streams.

Log	Supported engine versions
Slow log	Valkey 7.x and later, Redis OSS 6.0 and later
Engine log	Valkey 7.x and later, Redis OSS 6.2 and later

Log delivery isn’t supported for ElastiCache Serverless caches. It’s available for self-designed (node-based) clusters and replication groups only.

​

Recommended method

Amazon Data Firehose — enable log delivery for the slow log and/or engine log on the cluster, destination Amazon Data Firehose. Both log streams are supported.

Select the JSON log format on the AWS side. Bronto parses and flattens JSON records automatically — no parser needed. The TEXT format is comma-delimited and stored raw, requiring a custom parser. See Record formats.

​

Alternatives

• CloudWatch Log Forwarder — enable slow log and engine log delivery to CloudWatch on the cluster, and the Bronto forwarder Lambda subscribes to the resulting log groups.

See Ingesting AWS Data into Bronto for the full service-to-method mapping.

​

References

• Amazon ElastiCache — log delivery