> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/self-hosting/enterprise-self-hosting-byoc/deploy-hyperswitch-on-aws.md).

# Deploy on AWS

Deploy Hyperswitch on AWS using CloudFormation for full stack deployment or configure individual components independently

You can deploy it as an independent stack by leveraging our full-stack deployment solution. Alternatively, you can utilize the component-wise section to deploy it within an existing stack using a customized format.

Explore the details in each section for further information.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Full Stack Deployment (Recommended)</strong></mark></td><td>Deploy all components of Juspay Hyperswitch on-premise on AWS at once</td><td></td><td></td><td><a href="/self-hosting/enterprise-self-hosting-byoc/deploy-hyperswitch-on-aws/deploy-on-aws-using-cloudformation.md">Deploy on AWS using CloudFormation</a></td></tr><tr><td><mark style="color:blue;"><strong>Component-wise Deployment</strong></mark></td><td>Deploy the app server, control center, web client and card vault independently</td><td></td><td></td><td><a href="/self-hosting/enterprise-self-hosting-byoc/deploy-hyperswitch-on-aws/component-wise-deployment.md">Component-wise Deployment</a></td></tr></tbody></table>


---

# 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.hyperswitch.io/self-hosting/enterprise-self-hosting-byoc/deploy-hyperswitch-on-aws.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.