agreeable-window-77899
05/20/2022, 12:53 PMgreat-sunset-355
05/20/2022, 1:29 PMagreeable-window-77899
05/20/2022, 1:32 PMgreat-sunset-355
05/20/2022, 1:43 PMdependsOn
, 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_paramsagreeable-window-77899
05/20/2022, 2:06 PMone-off
execution so that it executes and exits and never really comes back up again.?clever-sunset-76585
05/23/2022, 3:17 PMessential
property to false
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-77899
05/23/2022, 3:24 PMclever-sunset-76585
05/23/2022, 3:35 PMessential
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-77899
05/23/2022, 3:37 PMcurved-pharmacist-41509
05/23/2022, 10:41 PM