# Deploying Weaviate on AWS

This section provides comprehensive guidance for deploying and running Weaviate on Amazon Web Services (AWS). Whether you're setting up a development environment, deploying to production, or integrating with AWS services, you'll find AWS-specific installation guides, tutorials, how-tos, and reference materials tailored for the AWS ecosystem.

## Deployment options

Weaviate has multiple pathways to deploy on AWS, each suited to different use cases and operational needs:

### Marketplace offerings

#### [AWS marketplace - Shared Cloud](../deploy-aws/aws-marketplace.md)

Deploy Weaviate Shared Cloud directly through the AWS Marketplace for quick cloud deployment with AWS billing integration.

This SaaS solution is specifically built for AWS customers who need:

- AWS billing integration
- Regulatory requirements with specific regional deployments
- Quick setup without infrastructure management

#### Resources Created:

- EKS Cluster with single node group
- Load Balancer Controller for EKS
- AWS EBS CSI driver for persistent storage
- Latest selected version of Weaviate via official Helm chart

**Best for**: Production environments, teams wanting managed Kubernetes without setup complexity, enterprise-grade deployments.

#### Specifications:

- Single EC2 instance (default: m7g.medium)
- Docker container deployment
- Monthly contract (billed immediately through AWS)
- Best for testing and development (no enterprise support included)

### Self-managed options

#### [Self-managed EKS](../deploy-aws/eks.md)

Create and manage your own EKS cluster using the `eksctl` command-line tool, providing full control over cluster configuration, scaling, and management.

#### Features:

- Complete control over cluster configuration
- Custom autoscaling node groups
- Choice of instance types and storage classes
- Integration with AWS EBS CSI driver for persistent storage

**Best for:** Organizations with Kubernetes expertise, custom infrastructure requirements, maximum flexibility and control

### Deployment comparison

![deployment comparison matrix](/assets/docs/deploy/production/aws/img/deployment-matrix.png)

Each deployment option offers different levels of management and control:

- **Shared Cloud:** Fully managed SaaS with automatic scaling and zero infrastructure management.
- **Marketplace EKS:** Managed Kubernetes control plane with pre-configured infrastructure via CloudFormation.
- **Marketplace EC2:** Single-instance Docker deployment with monthly billing, ideal for development.
- **Self-Managed EKS:** Complete control over EKS cluster configuration and management.

## Questions and feedback

Have a question or feedback? Here's how to reach us.

::::card-grid
:::card{title="Community Forum" href="https://forum.weaviate.io/c/support" icon="messages-square"}
Ask questions and connect with other developers on our **Community forum**.
:::

:::card{title="Support" href="/guides/support-overview" icon="life-buoy"}
Weaviate Cloud user or customer? Find the right channel on the **Support page**.
:::
::::

## Related pages

- [Agents](./agents-index.md)
- [AI-assisted Weaviate code generation](./ai-assisted-vibe-coding-index.md)
- [APIs](./apis-index.md)
- [Authorization and authentication](./authorization-and-authentication-index.md)
- [Benchmarks](./benchmarks-index.md)
- [Best practices](./best-practices-index.md)
- [Client libraries](./clients-index.md)
- [Client Libraries / SDKs](./client-libraries-index.md)
- [Cloud](./cloud-index.md)
- [Cloud account management](./cloud-account-management-index.md)

# Agent Instructions

This portal answers questions programmatically. To receive a synthesized,
source-cited answer instead of crawling page by page, append the `?ask=`
query parameter to any page URL on this site:

    /guides/quickstart?ask=how+do+I+authenticate

Optional parameters:

- `&goal=<what-you-are-trying-to-do>` steers the answer toward your
  objective (e.g. `&goal=write+a+python+client`).
- `&version=<label>` scopes the answer to a mounted version when the
  portal publishes more than one.

The response is `text/markdown`: the answer followed by a `# Sources` list
of the portal pages it was grounded in. Status codes are the contract:

- `200` — the answer; `402` — the portal owner’s plan or answer credits are
  exhausted (surface this to your operator; do NOT retry); `429` — you are
  rate-limited; back off for the `Retry-After` seconds; `503` — the answer
  lane is temporarily unavailable; fall back to crawling the `.md` pages.

For the full corpus map read `llms.txt` at the site root; for the tool
surface (search + page fetch as MCP tools) see `/mcp`.