<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Migration on FivexL. Cloud Engineering Specialists</title><link>/tags/migration/</link><description>Recent content in Migration on FivexL. Cloud Engineering Specialists</description><generator>Hugo</generator><language>en-US</language><managingEditor>info@fivexl.io (FivexL)</managingEditor><webMaster>info@fivexl.io (FivexL)</webMaster><lastBuildDate>Thu, 09 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/migration/index.xml" rel="self" type="application/rss+xml"/><item><title>What to Consider When Migrating from AWS App Runner to Amazon ECS</title><link>/blog/aws-app-runner-deprecation-migrate-to-ecs/</link><pubDate>Thu, 09 Jul 2026 00:00:00 +0000</pubDate><author>info@fivexl.io (FivexL)</author><guid>/blog/aws-app-runner-deprecation-migrate-to-ecs/</guid><description>&lt;p&gt;On March 31, AWS announced it is deprecating AWS App Runner. New customers were cut off on April 30, and while AWS has not yet published a final sunset date, the direction is clear: teams running on App Runner need a migration plan.&lt;/p&gt;
&lt;p&gt;AWS&amp;rsquo;s official migration guide &lt;sup&gt;[1]&lt;/sup&gt; points at Amazon Elastic Container Service (Amazon ECS) Express Mode. Express Mode is a reasonable starting point for prototyping, but for production workloads we recommend going straight to ECS on AWS Fargate. That way your lower environments and production use the same runtime, and you inherit the security controls App Runner abstracted away.&lt;/p&gt;
&lt;div style="background: linear-gradient(135deg, #f0f9ff 0%, #e0f2fe 100%); border-left: 4px solid #18AEF0; border-radius: 8px; padding: 1.5rem; margin: 1.5rem 0;"&gt;
&lt;p&gt;Below: what changes when App Runner disappears, why we skip Express Mode for production, and the security and networking details AWS&amp;rsquo;s migration guide leaves out.&lt;/p&gt;
&lt;/div&gt;</description></item></channel></rss>