Infrastructure Configuration
Self-Hosted Styra DAS operates on a “shared responsibility model” where Styra addresses customer-reported issues and patching vulnerabilities with Styra DAS microservices. The customer is responsible for configuring and maintaining the underlying infrastructure and configuration of the individual microservices per the recommendations provided by Styra. This section provides guidance to ensure compatibility between customer-configured infrastructure and Styra DAS but is not meant as a comprehensive guide on how to run cloud resources.
The following infrastructure configurations are currently used in existing customer environments. The installation instructions are included as guidance rather than as a guarantee of compatibility. If there are any installation issues, please contact your Customer Success Account Manager.
For each cloud provider, refer to the provider’s documentation for installing and configuring individual resources.
Running Self-Hosted Styra DAS requires a skilled team experienced with Kubernetes and infrastructure administration. Styra’s DAS SaaS offering abstracts the infrastructure management required to run Styra DAS and is fully qualified.
It is recommended to use Styra DAS SaaS unless there is a specific business requirement to use Self-Hosted Styra DAS.
At a high-level Styra DAS requires the following infrastructure components:
- Kubernetes cluster
- Database or Data Store (most commonly PostgreSQL)
- Elasticsearch
The following diagram shows examples of the most common infrastructure configurations used with Styra DAS.
Self-Hosted Styra DAS Configuration Options