Log Retention | John Nessime

The Real Cost of CloudWatch: Logs, Metrics, Retention and Cardinality

Post category:Cloud Computing FinOps Monitoring

CloudWatch rarely fails loudly, it accumulates. This is a breakdown of the four independent meters behind the bill: ingestion, storage, Logs Insights scans and custom metric cardinality. Why the same log line gets billed three times, why log groups never expire by default, how a single dimension can multiply your metrics bill without your traffic changing, and how to attribute the spend to specific log groups before you start deleting things.

Where PHI Escapes: Building a Secure Medical Lab Data Pipeline on AWS

Post category:Cloud Computing Cloud Security Compliance Data Engineering

Encryption is the part everyone gets right. The PHI sitting in your logs, dead letter queues and object key names is the part that fails an audit. A boundary-by-boundary guide to building a medical lab data pipeline on AWS that survives review.

Docker Logs Ate My Disk: A Working Guide to Log Drivers and Rotation

Post category:DevOps Docker System Administration Troubleshooting

Docker's default logging driver writes container output to a JSON file with no size limit and no rotation. This is a practical guide to Docker log rotation: what the defaults actually do, why your daemon.json change did nothing, why deleting the log file did not free any disk, and how to choose between json-file, local, journald and shipping logs off the box.

journald vs rsyslog: Where Your Linux Logs Actually Live

Post category:DevOps Linux System Administration

On a stock Linux server, journald and rsyslog are both running and both storing the same events, with retention policies that don't know about each other. Here's where each log line actually lives, the three failure modes that bite in production, and how to decide which copy you keep.

HIPAA Compliance on AWS: The Gaps That Pass Every Security Check

Post category:Case Studies Cloud Computing Technical Guides Web Security

A working engineer's guide to HIPAA compliance on AWS, organised by the gap between the control you configured and the obligation you actually carry. Covers BAA account scope, the eligible services list as a contract boundary, KMS key policy versus the encryption checkbox, what "six years" really applies to, backup and restore scope, and the subprocessor chain nobody inventories.