<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>ECS on Tony Zaarour</title>
    <link>https://bio.zaalocal.uk/tags/ecs/</link>
    <description>Recent content in ECS on Tony Zaarour</description>
    <image>
      <title>Tony Zaarour</title>
      <url>https://bio.zaalocal.uk/logo.gif</url>
      <link>https://bio.zaalocal.uk/logo.gif</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 18 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://bio.zaalocal.uk/tags/ecs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Modernising long-running workloads with event-driven ECS tasks</title>
      <link>https://bio.zaalocal.uk/posts/modernising-long-running-workloads-with-event-driven-ecs-tasks/</link>
      <pubDate>Wed, 18 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://bio.zaalocal.uk/posts/modernising-long-running-workloads-with-event-driven-ecs-tasks/</guid>
      <description>Some workloads do not belong inside a permanent service. Moving them into event-driven ECS tasks can improve isolation, scaling, and cost control.</description>
    </item>
    
    <item>
      <title>Analyzing ECS Task Status with Python and Boto3</title>
      <link>https://bio.zaalocal.uk/projects/ecs_report/</link>
      <pubDate>Sun, 12 Jun 2022 18:08:42 -0400</pubDate>
      
      <guid>https://bio.zaalocal.uk/projects/ecs_report/</guid>
      <description>Let&amp;rsquo;s say you updated all ECS clusters and forced new deployment, you can generate a report on the status of all ECS in one simple script</description>
    </item>
    
  </channel>
</rss>
