<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fortem Blog</title>
    <link>https://fortem.dev/blog</link>
    <description>Guides, comparisons, and use cases for platform engineers running AWS ECS Fargate at scale.</description>
    <language>en-us</language>
    <lastBuildDate>Tue, 09 Jun 2026 23:08:36 GMT</lastBuildDate>
    <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
    <atom:link href="https://fortem.dev/feed.xml" rel="self" type="application/rss+xml" />
    <generator>fortem-dev feed</generator>
    <item>
      <title>Do You Need an Internal Developer Platform for AWS ECS?</title>
      <link>https://fortem.dev/blog/internal-developer-platform-ecs/</link>
      <guid isPermaLink="true">https://fortem.dev/blog/internal-developer-platform-ecs/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <category>Guide</category>
      <description>93% of top-performing teams use an IDP. But ECS teams don&apos;t need a full platform — they need an operational layer. A decision framework to figure out what you actually need.</description>
    </item>
    <item>
      <title>How to Clone an ECS Environment Without Rewriting Terraform?</title>
      <link>https://fortem.dev/blog/ecs-environment-clone/</link>
      <guid isPermaLink="true">https://fortem.dev/blog/ecs-environment-clone/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <category>Use Case</category>
      <description>The compliance auditor wants a clone of production. That&apos;s 15 services, an ALB, RDS, SSM params — a 12-step manual process. Here&apos;s the template approach, and a parameterized Terraform module.</description>
    </item>
    <item>
      <title>Why Can&apos;t You See Per-Environment AWS Costs?</title>
      <link>https://fortem.dev/blog/ecs-fargate-cost-visibility/</link>
      <guid isPermaLink="true">https://fortem.dev/blog/ecs-fargate-cost-visibility/</guid>
      <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
      <category>Use Case</category>
      <description>Cost Explorer shows the total. It doesn&apos;t show per-environment costs. Here&apos;s why ECS Fargate environments are structurally hard to attribute — and a 10-line bash script that does it anyway.</description>
    </item>
    <item>
      <title>Fortem vs Cortex: Which Tool Actually Operates Your ECS Fleet?</title>
      <link>https://fortem.dev/blog/fortem-vs-cortex/</link>
      <guid isPermaLink="true">https://fortem.dev/blog/fortem-vs-cortex/</guid>
      <pubDate>Thu, 04 Jun 2026 00:00:00 GMT</pubDate>
      <category>Versus</category>
      <description>Cortex is an Engineering Operations Platform for org-wide visibility. Fortem operates your ECS Fargate fleet specifically. Here&apos;s which one you need — and when to use both.</description>
    </item>
    <item>
      <title>How Much Do AWS Dev Environments Really Cost?</title>
      <link>https://fortem.dev/blog/aws-dev-environment-cost/</link>
      <guid isPermaLink="true">https://fortem.dev/blog/aws-dev-environment-cost/</guid>
      <pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate>
      <category>Guide</category>
      <description>Cost Explorer shows the total. It doesn&apos;t show per-environment costs. Here&apos;s the real math: compute + fixed overhead (ALB, NAT, CloudWatch ≈ $90/env) — and how to see it.</description>
    </item>
    <item>
      <title>What Does DevOps Automation Miss Beyond CI/CD?</title>
      <link>https://fortem.dev/blog/devops-automation-beyond-cicd/</link>
      <guid isPermaLink="true">https://fortem.dev/blog/devops-automation-beyond-cicd/</guid>
      <pubDate>Tue, 02 Jun 2026 00:00:00 GMT</pubDate>
      <category>Guide</category>
      <description>CI/CD automates deployment — not operations. 5 gaps every team discovers at 10+ environments: scheduling, self-service, cost tracking, cloning, orphans. Build vs buy breakdown.</description>
    </item>
    <item>
      <title>ECS Fargate Best Practices: Running a Fleet of 10+ Environments Without the Pain</title>
      <link>https://fortem.dev/blog/ecs-fargate-best-practices/</link>
      <guid isPermaLink="true">https://fortem.dev/blog/ecs-fargate-best-practices/</guid>
      <pubDate>Mon, 01 Jun 2026 00:00:00 GMT</pubDate>
      <category>Guide</category>
      <description>Seven Fargate best practices for teams at scale: naming conventions, fixed overhead, CloudWatch retention, Fargate Spot, quota isolation, Terraform state, and scheduling. Real numbers from AWS pricing.</description>
    </item>
    <item>
      <title>How to Cut AWS Costs Without Reserved Instances</title>
      <link>https://fortem.dev/blog/reduce-aws-costs-without-ri/</link>
      <guid isPermaLink="true">https://fortem.dev/blog/reduce-aws-costs-without-ri/</guid>
      <pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate>
      <category>Guide</category>
      <description>RIs and Savings Plans change how you pay, not what runs. Here are 5 methods that cut actual consumption — scheduling, right-sizing, Spot, auto-stop, and killing orphans — ranked by impact.</description>
    </item>
    <item>
      <title>What Does AWS Fargate Actually Cost Per Environment?</title>
      <link>https://fortem.dev/blog/aws-fargate-pricing-real-costs/</link>
      <guid isPermaLink="true">https://fortem.dev/blog/aws-fargate-pricing-real-costs/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <category>Guide</category>
      <description>AWS says $0.04048/vCPU-hr. Here&apos;s what a real environment costs — ALB, NAT Gateway, CloudWatch, data transfer — and the fixed overhead nobody budgets for.</description>
    </item>
    <item>
      <title>Managing ECS Fargate with Terraform: What Works and What Doesn&apos;t</title>
      <link>https://fortem.dev/blog/ecs-fargate-terraform/</link>
      <guid isPermaLink="true">https://fortem.dev/blog/ecs-fargate-terraform/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <category>Guide</category>
      <description>Terraform is the right tool for provisioning ECS Fargate infrastructure. But at 10+ environments, state sprawl and the ops gap catch every team. Three patterns, a tagging strategy, and what the operations layer needs to do.</description>
    </item>
    <item>
      <title>ECS Multi-Environment Strategy: What Breaks at 10 That Worked Fine at 3</title>
      <link>https://fortem.dev/blog/ecs-multi-environment-strategy/</link>
      <guid isPermaLink="true">https://fortem.dev/blog/ecs-multi-environment-strategy/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <category>Guide</category>
      <description>Naming conventions, cluster structure, and the five AWS limits that surface when environments scale from 3 to 10+. Fixed overhead, IAM proliferation, Fargate quota exhaustion — and what to get right before you hit the wall.</description>
    </item>
    <item>
      <title>ECS Environment Scheduling: The Complete Guide</title>
      <link>https://fortem.dev/blog/ecs-environment-scheduling/</link>
      <guid isPermaLink="true">https://fortem.dev/blog/ecs-environment-scheduling/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <category>Guide</category>
      <description>Stop paying for ECS dev and staging environments when nobody&apos;s using them. Every scheduling approach — AWS-native options, trade-offs, and what actually works at fleet scale.</description>
    </item>
    <item>
      <title>AWS Proton is Deprecated: What ECS Teams Should Do Before October 7</title>
      <link>https://fortem.dev/blog/aws-proton-deprecated/</link>
      <guid isPermaLink="true">https://fortem.dev/blog/aws-proton-deprecated/</guid>
      <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
      <category>Timely</category>
      <description>AWS Proton shuts down October 7, 2026. Your ECS environments keep running — but the console, APIs, and every pipeline built on Proton stop working. Here&apos;s what breaks and how to migrate.</description>
    </item>
    <item>
      <title>It&apos;s Friday at 6pm. Your Developer Can&apos;t Restart Staging Without You.</title>
      <link>https://fortem.dev/blog/ecs-staging-self-service/</link>
      <guid isPermaLink="true">https://fortem.dev/blog/ecs-staging-self-service/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <category>Use Case</category>
      <description>Platform engineers become the single point of failure for staging ops when developers have no safe, scoped way to act. Here&apos;s how to fix it with ECS environment RBAC.</description>
    </item>
    <item>
      <title>AWS Copilot is Deprecated: Alternatives for ECS Fargate Teams</title>
      <link>https://fortem.dev/blog/fortem-vs-aws-copilot/</link>
      <guid isPermaLink="true">https://fortem.dev/blog/fortem-vs-aws-copilot/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <category>Versus</category>
      <description>AWS Copilot CLI reaches end-of-support June 12, 2026. Your ECS services keep running — but here&apos;s what breaks, what to do next, and how to migrate.</description>
    </item>
    <item>
      <title>Fortem vs Flightcontrol: ECS Fleet Management vs Single-App PaaS</title>
      <link>https://fortem.dev/blog/fortem-vs-flightcontrol/</link>
      <guid isPermaLink="true">https://fortem.dev/blog/fortem-vs-flightcontrol/</guid>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <category>Versus</category>
      <description>Flightcontrol is the right tool for 1–3 apps on AWS. Here&apos;s exactly where it stops making sense — and where the pricing math breaks at fleet scale.</description>
    </item>
    <item>
      <title>How to Cut AWS ECS Fargate Costs by 60–70%</title>
      <link>https://fortem.dev/blog/ecs-fargate-cost-optimization/</link>
      <guid isPermaLink="true">https://fortem.dev/blog/ecs-fargate-cost-optimization/</guid>
      <pubDate>Sat, 23 May 2026 00:00:00 GMT</pubDate>
      <category>Guide</category>
      <description>Dev/staging environments run 168 hrs/week. Your team works 40. Here&apos;s the math on what that costs — and four methods to fix it, starting with the one most teams ignore.</description>
    </item>
  </channel>
</rss>
