From 823306bf9fe32d4c34ca2dfd5c4e70638abf66da Mon Sep 17 00:00:00 2001 From: Savin Date: Tue, 29 Jul 2025 14:06:34 -0700 Subject: [PATCH] Update spot-instances.md --- docs/scaling/remote-tasks/spot-instances.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/scaling/remote-tasks/spot-instances.md b/docs/scaling/remote-tasks/spot-instances.md index b403c293..da2d1fc0 100644 --- a/docs/scaling/remote-tasks/spot-instances.md +++ b/docs/scaling/remote-tasks/spot-instances.md @@ -8,9 +8,6 @@ discounted price compared to on-demand instances. However, these instances can be interrupted with a short notice when the cloud provider needs the capacity back. -:::info -Spot instance support is currently available with `@kubernetes` and `@batch` decorator on AWS. -::: ## Retrying and resuming tasks running on spot instances @@ -82,6 +79,10 @@ termination notice file using `current.spot_termination_notice`. When a termination notice is detected, the task can perform any necessary cleanup and checkpointing before the instance is reclaimed. +:::info +Spot termination notice support is currently available with `@kubernetes` and `@batch` decorator on AWS. +::: + ## Testing Spot Instance Interruptions You can use the AWS FIS (Fault Injection Service) to test how your tasks handle spot instance