> ## Documentation Index
> Fetch the complete documentation index at: https://aspect.build/llms.txt
> Use this file to discover all available pages before exploring further.

# Spot instances for remote execution workers on AWS

> Aspect Enterprise remote execution worker pools on AWS can run on EC2 Spot capacity, per pool, with the cache kept on-demand.

[← Shipped](https://aspect.build/shipped)

# Spot instances for remote execution workers on AWS

***

![A worker pool with one on-demand instance and several Spot instances, writing to cache storage that stays on-demand](https://mintlify.s3.us-west-1.amazonaws.com/aspectbuild/images/marketing/illustrations/shipped-spot-rbe-workers.svg)

A remote execution worker holds no state you care about. It fetches inputs from the cache, runs an action, and writes the outputs back. That's the workload EC2 Spot is priced for.

On Aspect Enterprise on AWS, a remote execution worker pool can now run on Spot. It's per pool and off by default: set `ec2.use_spot = true` on the pool in a self-hosted deployment, or ask Aspect to turn it on for a deployment hosted by Aspect.

## What you get

* **A Spot and on-demand mix.** `ec2.instance_policy` sets the on-demand base and percentage, the Spot allocation strategy, a max price, and the instance types to draw from.
* **On-demand cache.** Spot applies to workers only. Cache storage stays on-demand.

[Remote execution on Aspect Enterprise](https://aspect.build/docs/aspect-workflows/enterprise/remote-execution.md) covers worker pools and what else you configure on each one.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.