Skip to content

Update spot-instances.md #154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 29, 2025
+4 −3
Merged

Update spot-instances.md #154

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions docs/scaling/remote-tasks/spot-instances.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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
Expand Down
Loading