agreeable-window-7789905/20/2022, 12:53 PM
great-sunset-35505/20/2022, 1:29 PM
agreeable-window-7789905/20/2022, 1:32 PM
great-sunset-35505/20/2022, 1:43 PM
, read up on ECS docs https://docs.aws.amazon.com/AmazonECS/latest/developerguide/welcome-features.html https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#other_container_definition_params
agreeable-window-7789905/20/2022, 2:06 PM
execution so that it executes and exits and never really comes back up again.?
clever-sunset-7658505/23/2022, 3:17 PM
for your migration container to prevent it from being restarted. However, I think if your migration container exits on failure it won't stop the other container from starting up, assuming you want that sort of control. You might need to achieve that through some other means by detecting that the migration container exited with failure status code and handle that however that's appropriate to you.
agreeable-window-7789905/23/2022, 3:24 PM
clever-sunset-7658505/23/2022, 3:35 PM
set to false and detect if the container exited with a failure status code. You'd have do that detection no matter which service you choose -- Lambda or Fargate. As for which is better, it's hard to say. It depends on a few factors. Each has its benefits of being "better" than the other. Choose what makes sense to you and what you need right now.
agreeable-window-7789905/23/2022, 3:37 PM