> For the complete documentation index, see [llms.txt](https://docs.warpstream.com/warpstream/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.warpstream.com/warpstream/agent-setup/infrastructure-as-code/terraform-modules.md).

# Terraform Modules

To make deployment of WarpStream easier we have published Terraform modules and examples for various services.

### AWS - Elastic Container Service

Source: <https://github.com/warpstreamlabs/terraform-aws-warpstream-ecs>

This module creates an ECS cluster, a S3 storage bucket, IAM Roles, an ECS Task, and an ECS Service running the WarpStream Agent.

This module assumes you already have a VPC with a NAT Gateway to the internet. Internet access is needed to be able to pull the WarpStream Agent container image.

A fully working example can been seen here: <https://github.com/warpstreamlabs/terraform-aws-warpstream-ecs/tree/main/examples/basic>

### AWS - Elastic Kubernetes Service

Source: <https://github.com/warpstreamlabs/terraform-aws-warpstream-eks>

This module creates an EKS cluster, a S3 storage bucket, IAM Roles, and deploys the WarpStream Agent helm chart.

This module assumes you already have a VPC with a NAT Gateway to the internet. Internet access is needed to be able to pull the WarpStream Agent container image.

A fully working example can been seen here: <https://github.com/warpstreamlabs/terraform-aws-warpstream-eks/tree/master/examples/basic>


---

# 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.warpstream.com/warpstream/agent-setup/infrastructure-as-code/terraform-modules.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.