Platform Engineering

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 #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# 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

TCP #122: Your approval process needs a classification model, not just a queue

Three-tier framework, change matrix, and checklist for what platform must own, review, or release.

May 13 • Amrut Patil

TCP #121: Accountability Without Authority Is How Platform Teams Fail

When platform is judged on reliability, cost, and compliance without approval rights over infrastructure, failure is structural, not personal.

May 10 • Amrut Patil

TCP #120: The Infrastructure Ownership Matrix For Platform And App Teams

A practical way to decide who can provision which AWS resources, under what conditions, and with whose approval.

May 6 • Amrut Patil

TCP #118: The Platform Intake Operating Model For Scaling Platform Teams

How to replace Slack chaos with a routing matrix, approval tiers, and rollout plan your platform team can actually live with

Apr 30 • Amrut Patil

TCP #117: Your platform team doesn’t have a capacity problem.

4 structure checks to recover 30–40% of their time without hiring.

Apr 26 • Amrut Patil

TCP #116: Most teams don't have a technical debt problem.

They have a decision debt problem. The distinction changes what you measure, build, and protect.

Apr 12 • 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