No, AWS Batch does not support EC2 spot stop/start and hibernation options with a managed compute environment (CE). If a Spot instance is terminated, AWS Batch will retry the job (from the start) per your retry strategy defined in your job definition. It is possible for your job to resume progress if it has checkpointing built-in and you save your data somewhere that can be accessed again (e.g. EFS).
You can use hibernation with unmanaged CE. However, since it is not officially supported, your job might be “stuck” when Spot reclaims your instance and the instance goes into hibernation. This job will continue to be in “running” state and stay at the top of your job queue, preventing other jobs from running if you have hit your max vCPU limit in your CE.
Does using SPOT_CAPACITY _OPTIMIZED launch spot instances into an auto-scaling group in AWS Batch?asked 5 months ago
Can't launch ec2 spot instance with hibernation for instance type c5.18xlarasked 2 years ago
My usecase for AWS BatchAccepted Answerasked 7 months ago
Batch and Spot InterruptionsAccepted Answerasked 5 years ago
How does hibernation impact snapshots within EC2?Accepted Answerasked 10 months ago
Does AWS Batch support EC2 Spot stop/start and hibernationAccepted Answerasked 4 years ago
Hibernation not working as expectedasked 10 months ago
AWS Fargate Spot - Automated Draining for Spot SupportAccepted Answerasked 3 years ago
AWS Spot Pricing Specificsasked 6 months ago
Hibernating Spot Instances upon interruption in Amazon EKSAccepted Answerasked 2 years ago