Skip to main content

Reducing Infrastructure Costs for Credential APIs

Question​

How can I use the credential-related APIs and import schema without the cost implications of using Vault, Redis, and Postgres?

Answer​

For operations involving credential-related APIs and schemas, certain components are indispensable, while others offer more flexibility:

  • Vault: Primarily used for securing private keys necessary for signing credentials and publishing states. Although crucial, you have the option to customize the storage solution for these keys, for instance, by storing them in files instead of using Vault directly. This approach allows for greater flexibility in managing infrastructure costs.
  • Redis: This is a required component for caching, contributing to the performance and efficiency of operations.
  • Postgres: It is essential for persisting credentials, schemas, connections, and more. Given its central role in the system's functionality, Postgres cannot be omitted.

To manage costs effectively, consider leveraging Docker Compose for local development or testing environments, which can significantly reduce expenses. For cloud deployments, the costs will largely depend on the chosen infrastructure services, such as EC2 instances. Careful selection and configuration of these services can help in controlling expenses without compromising the system's capabilities.

Additionally, for a streamlined deployment process, consider deploying the Issuer Node directly from the Google Marketplace. This option can provide a more integrated and potentially cost-effective cloud solution. Visit the following link for more details and deployment instructions: Polygon ID Issuer Node on Google Marketplace.

For additional insights or specific inquiries about minimizing infrastructure costs while maintaining operational efficiency, please feel free to reach out.