Archive - The Cloud Playbook

TCP #134: GuardDuty org-wide is a one-click decision with a six-month tail.

The pre-flight decisions on delegated admin, cost, and alert routing that decide whether GuardDuty becomes signal or noise.

Jul 19 • Amrut Patil

TCP #133: Permission sets belong in a pipeline, not in the Identity Center console

The controls-as-code system for permission sets: repo structure, CI/CD deployment, privilege review gates, and drift detection

Jul 16 • Amrut Patil

TCP #132: Your Control Tower guardrails belong in Terraform, not the console

The controls-as-code system for preventive, detective, and proactive guardrails, with review, drift detection, and rollout order.

Jul 12 • Amrut Patil

TCP #131: The multi-account checklist regulated SaaS teams should have written

Account strategy, identity, networking, tenancy, and audit — each section with owners, cadences, and evidence.

Jul 9 • Amrut Patil

TCP #130: Multi-Account AWS Environments Fail When Nobody Owns the Boundaries

Why account sprawl, tenant separation, and shared services break down without explicit control-plane ownership.

Jul 5 • Amrut Patil

TCP #129: The scoring framework that picks ECS, EKS, or Lambda.

A weighted decision matrix across team maturity, operations, compliance, cost, and ownership with worked examples.

Jul 2 • Amrut Patil

June 2026

TCP #128: ECS, EKS, and Lambda are not the same decision

How team maturity, operational burden, and tenancy reshape the AWS compute choice, and what teams get wrong by treating them as alternatives

Jun 28 • Amrut Patil

TCP #127: The ADR template that turns architecture into a written contract

Decision context, tradeoffs, risk, cost, compliance, and rollback captured in a format leadership can read.

Jun 21 • Amrut Patil

TCP #126: Architecture decisions are risk decisions. Most teams forget that.

How to evaluate AWS architecture choices on what they cost you in 18 months, not what they save you this sprint.

Jun 18 • Amrut Patil

TCP #125: The MBR template that changes how leadership funds platform.

Delivery, reliability, cost, security, and risk, formatted for the engineering leadership audience.

Jun 14 • Amrut Patil

May 2026

TCP# 124: The 6 golden paths worth building first, and how to sequence them.

Scored by frequency, friction, risk, and reach. With backlog template and adoption metrics.

May 24 • Amrut Patil

TCP #123: Golden paths fail when they require engineers to choose them

The difference between documentation and a system, and why one scales while the other doesn't.

May 17 • Amrut Patil

#nojs-banner { position: fixed; bottom: 0; left: 0; padding: 16px 16px 16px 32px; width: 100%; box-sizing: border-box; background: red; color: white; font-family: -apple-system, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; font-size: 13px; line-height: 13px; } #nojs-banner a { color: inherit; text-decoration: underline; } This site requires JavaScript to run correctly. Please turn on JavaScript or unblock scripts