What this means is that after April 1, 2021, although existing resources will keep running, we won’t be able to scale up/down our existing apps nor would we be able to recover from any failing ECS tasks (i.e., attempting to create a new ECS task will result in AWS to use the new format but it will fail to do so because the ECS service which those tasks belong will not be using the new format in the first place.)
Convox doesn’t support recreating an ECS service (i.e., a convox app) anew without downtime.
So far there was only one discussion that I am aware of in the convox community which doesn’t say much related to how the migration should happen in existing convox gen2 racks.
One way to approach this is to employ a blue-green deployment between the existing app and a new app I should create with the new configuration (i.e., an ECS service using the new ARN and resource ID format). Blue-green deployment requires a considerable amount of work and potential for service disruption if not executed correctly. We should all be hoping to avoid this option unless it is a last resort. It’s especially painful for products and services with many apps.
If I am reading this right I wonder why the community isn’t as worried as I am and if there’s a better way to do this in convox that I am missing.