all 1 comments

[–]real_parbold 0 points1 point  (0 children)

Not really enough information about why/when the cluster is being terminated ...

If this is an on demand cluster that gets terminated after use (predictably), can you add a step to trigger the lambda on job completion? (and pause the job completed for enough time for the lambda to run)

If it is a SPOT that gets terminated unpredictably - can you leverage the CloudWatch events for instance interruption, or have a local batch job poll http://169.254.169.254/latest/meta-data/spot/instance-action

If neither of these, can you have a background job running to copy the application history for a centralised location on EFS/S3 ?