Notes from delivery rather than from marketing. Problems we have actually hit, written up while the detail is still accurate. Published when there is something to say, which is not often.
Start a conversationFour posts, no schedule. This is not a content programme. Each of these came out of a specific problem in a specific week, and they are here because the answer was hard to find anywhere else. If that stops being true, nothing new appears.
A professional liability policy can look correct on every limit and still exclude the only thing a data engineering firm needs it for. The exact wording, why it rarely appears in the quote, and the question to ask every carrier before binding.
Read this postThe built-in monitoring in RDS and Aurora was deprecated on 30 June 2026. Nothing broke, which is the problem. How to tell whether your estate has a diagnostic gap, and what the realistic replacements actually cost.
Read this postRunning transactional traffic and pgvector similarity search on the same PostgreSQL cluster is convenient and cheap, and it quietly sets two workloads against each other. What to plan for before the wrong one starts degrading.
Read this postThere is no DISA STIG for most managed cloud databases. The Database Security Requirements Guide is the accepted proxy, roughly 142 controls, and the work is tractable if the remediation is written as code rather than clicked.
Read this postMost of these started as an assessment finding. If something here matches a problem in front of you, that is usually the fastest way in.