<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AWS Deployment Strategies on Edward Poot</title>
    <link>https://edwardpoot.com/series/aws-deployment-strategies/</link>
    <description>Recent content in AWS Deployment Strategies on Edward Poot</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 15 Aug 2025 11:41:00 +0200</lastBuildDate>
    <atom:link href="https://edwardpoot.com/series/aws-deployment-strategies/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Avoiding Pitfalls in AWS ECS Blue/Green Deployments</title>
      <link>https://edwardpoot.com/posts/aws-ecs-blue-green-deployments/</link>
      <pubDate>Fri, 15 Aug 2025 11:41:00 +0200</pubDate>
      <guid>https://edwardpoot.com/posts/aws-ecs-blue-green-deployments/</guid>
      <description>&lt;h1 id=&#34;mastering-bluegreen-deployments-in-aws-ecs-a-developers-guide&#34;&gt;Mastering Blue/Green Deployments in AWS ECS: A Developer&amp;rsquo;s Guide&lt;/h1&gt;&#xA;&lt;p&gt;Blue/green deployment is a powerful technique for minimizing downtime and risk during application updates. AWS Elastic Container Service (ECS) offers native support for this deployment strategy through its built-in blue/green deployment type. I&amp;rsquo;ll walk you through implementing blue/green deployments in AWS ECS, with special attention to a common configuration pitfall that many developers run into.&lt;/p&gt;&#xA;&lt;h3 id=&#34;understanding-bluegreen-deployments-in-ecs&#34;&gt;Understanding Blue/Green Deployments in ECS&lt;/h3&gt;&#xA;&lt;p&gt;Blue/green deployment is a release methodology where you maintain two identical production environments:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
