title: How to avoid "unstyled" app during ECS deployment?
body: <p>My express application is running in an amazon ECS container behind an ALB load balancer.</p>
  
  <p>For cachebusting webpack generates a new hash each time the app is built and released and appends it to the CSS file name (e.g. <code>main.b938eb5b2934c85d13e0.css</code>).</p>
  
  <p>During deployment of a new release, both containers (old version and new version) are running at the same time for about a minute and the LB routes requests to one of the containers randomly.</p>
  
  <p>It then sometimes happens that users get the <code>index.html</code> from the new container, but the following CSS request is routed to the old container, resulting in 404 because the hash part of the filename is different. Users then see a completely broken unstyled GUI.</p>
  
  <p>How can this be avoided this without losing the cachebusting aspect?</p>