> 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/component-wise-deployment/deploy-card-vault.md).
# Deploy Card Vault
Deploy the Juspay Hyperswitch Card Vault on the cloud
The Juspay Hyperswitch Card Vault [(Repo Link)](https://github.com/juspay/tartarus), is a highly performant and secure locker to save sensitive data such as payment card details, bank account details etc.
It is designed in a polymorphic manner to handle and store any type of sensitive information making it highly scalable with extensive coverage of payment methods and processors.
Tartarus is built with a GDPR compliant personal identifiable information (PII) storage and secure encryption algorithms to be fully compliant with PCI DSS requirements.
### How does it work?
* The Juspay Hyperswitch application communicates with Tartarus via a middleware.
* All requests and responses to and from the middleware are signed and encrypted with the JWS and JWE algorithms.
* The locker supports CRD APIs on the /data and /cards endpoints - [API Reference](https://api-reference.hyperswitch.io/api-reference/cards/add-data-in-locker)
* Cards are stored against the combination of merchant and customer identifiers.
* Internal hashing checks are in place to avoid data duplication.
### Key Hierarchy
Master Key - AES generated key to that is encrypted/decrypted by the custodian keys to run the locker and associated configurations.
Custodian Keys - AES generated key that is used to encrypt and decrypt the master key. It is broken into two keys (`key 1` and `key 2`) and available with two custodians to enhance security.
### Setting up your Card Vault
Automated deployment of Card Vault as a standalone component
---
# 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/component-wise-deployment/deploy-card-vault.md?ask=&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.