The following section provides an overview of the Styra Self-Hosted DAS Installation Guide, Styra DAS, Styra DAS architecture, and the microservices used with Styra DAS.
Document Overview and Audience
The Self-Hosted Styra DAS Installation Guide contains information on configuring and installing Styra DAS on a wide selection of cloud infrastructure providers. The contents of the Infrastructure Configuration and the Cloud Agnostic Infrastructure sections are not, however, meant to be a comprehensive guide to cloud infrastructure. The infrastructure sections of this document are intended to provide guidance specific to configuring and instantiating infrastructure for use with Styra DAS. Accordingly, this document assumes the customer is familiar with managing their own infrastructure and defers to provider-specific documentation wherever possible.
Styra DAS can also run on self-managed or non-cloud infrastructure. Such setups, however, tend to require customized support and compatibility patterns. If you cannot utilize any of the providers described in this document, we recommend working with Styra’s Sales and Solutions Architecture teams to determine the best method of deploying Styra DAS on your infrastructure.
Styra DAS Microservices
The following table describes the Styra DAS microservices used in Self-Hosted Styra DAS.
|Styra DAS Microservice
|Provides user activity log APIs.
|Constructs and serves policy bundles.
|Loads decision logs from OPA to Elasticsearch for indexing.
|APIs for OPAs to send status updates and decision logs.
|Caches OPA status updates for quick retrieval.
|APIs to search decision logs.
|Required to enable mock-opa sandbox environments.
|Shards work across service replicas.
|Executes Data Sources that require pulling data.
|Search engine for decision logs.
|Manages storage resources for the environment.
|Configuration management APIs.
|API gateway. All API requests are routed through the gateway. It enforces authentication and authorization and records user activity.
|Optional second API gateway.
|Optional telemetry reporting service.
|APIs to assess the impact of a policy change on previous decisions.
|Enables the monitoring integrations described in Monitoring Integrations.
|Decision mocking for sandbox environments.
|APIs for policy management.
|Stack configuration and management APIs.
|PostgreSQL for all internal, persisted states.
|System configuration and management APIs, OPA configuration bundle APIs used for discovery.
|Configures and manages the tenant's internal state.
|Computes metrics over decision log APIs
|Peer-to-peer framework and service that enables distributed in-memory storage. It implements horizontal communications between service instances, data sharing, and update/event notifications.