> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/4.1/install/aws/aws-outposts-deployment.md).

# AWS outposts deployment

This page describes how to install WEKA on AWS Outposts

## Overview

[AWS Outposts](https://aws.amazon.com/outposts/) is a fully managed service that extends AWS infrastructure, AWS services, APIs, and tools to virtually any data center, co-location space, or on-premises facility for a consistent hybrid experience. AWS Outposts is ideal for workloads that require low latency access to on-premises systems, local data processing, or local data storage.

## Deployment of a WEKA cluster in AWS outposts

A WEKA cluster deployment in AWS Outposts follows the guidelines described in the [Deployment types](/4.1/install/aws/deployment-types.md) section.

To deploy a WEKA cluster in AWS Outposts, use a CloudFormation template, which can be obtained as described in the [CloudFormation template Generator](/4.1/install/aws/cloudformation.md) section.

{% hint style="warning" %}
**Note:** AWS Outposts do not currently support placement groups, so the placement group from the template should be removed.
{% endhint %}

This template can be customized. For further assistance, contact the [Customer Success Team](/4.1/support/getting-support-for-your-weka-system.md#contact-customer-success-team).


---

# 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.weka.io/4.1/install/aws/aws-outposts-deployment.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.