AWS Cloud

TCP #139: The strangler fig that strangled nothing after 18 months

How to sequence which seam gets cut first, second, and third, so the pattern converges instead of stalling at two services forever.

Aug 16 • Amrut Patil

TCP #138: The rehost business case that was true in the slide deck

Three line items that turn a lift-and-shift savings story into a loss, and where each one hides until the first invoice.

Aug 9 • Amrut Patil

TCP #137: The migration strategy meeting that never needed to be a meeting.

Four questions that sort any workload into rehost, replatform, refactor, repurchase, retain, or retire, before the debate starts.

Aug 1 • Amrut Patil

TCP#136: You picked your secret store by cost. That was the wrong axis.

Secrets Manager, Parameter Store, and KMS-encrypted env compared on the axes that actually decide the right store per secret.

Jul 26 • Amrut Patil

TCP #135: The GuardDuty org-wide gotchas that break your Terraform run

Delegated admin, per-feature enablement, severity routing, and the multi-region and provider traps, all as code

Jul 23 • Amrut Patil

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

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 #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 #119: Platform Teams Do Not Scale by Saying Yes Faster

Most platform bottlenecks come from unclear intake, routing, approvals, and ownership, not a lack of headcount.

May 4 • Amrut Patil

TCP #107: Database Architecture for Multi-Tenant Platforms: The Tradeoffs Nobody Explains Well

What I would build differently and the one rule I enforce at tenant onboarding now.

Mar 11 • 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