> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/help-center/guaranteed-commitments/low-capacity-instances.md).

# Low Capacity Instances (GPUs)

## On AWS

There are multiple types of commitments that AWS offers, some of which — like Zonal Standard Reserved Instances (RIs) — come bundled with a capacity reservation to ensure access to the underlying machine being covered. See [AWS capacity reservations documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-capacity-reservations.html) for more details.

By default, Archera Guaranteed Commitments are created from Regional Standard RIs or Savings Plans, which don't come with a capacity reservation; however, they can synergize with an existing capacity reservation to provide a billing discount.

In certain circumstances — particularly with machines like GPUs that have low-capacity-availability — Archera supports creating Guaranteed RIs (GRIs) from **Zonal Standard RIs**, which do come with a capacity reservation and can give customers the peace of mind that they will always have access to spin up the machine they are committed to.

Please note that this is **not the default GRI option** and you will have to contact us in order to make use of this option.

If you are interested in using Zonal GRIs with a capacity reservation, please contact <support@archera.ai> to learn more.

## Related Resources

* [How Does Guaranteed Commitment Pricing Work?](/help-center/guaranteed-commitments/pricing.md)
* [What are Guaranteed Commitments?](/help-center/guaranteed-commitments/what-are-guaranteed-commitments.md)
* [Does Archera support On Capacity Demand Reservations? (OCDR)](/help-center/faq/ocdr.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.archera.ai/help-center/guaranteed-commitments/low-capacity-instances.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.