Architecture Overview

Upriver as a software-as-a-service with options to deploy parts of the platform into the customer's environment for security and compliance requirements.

Components

• Upriver's Cloud Service - Service supporting the user interface, data monitoring system, reliability dashboards, and notification routing.

• Upriver's Data Storage - An object storage bucket in which all of the extracted metrics are stored as well as a small number of samples that are used to help in the Root Cause Analysis for detected incidents.

• Upriver's Data Analyzer - A workload running on lambda instances used to monitor the data. This workload assumes the read-role specified by the user and stores the extracted insights into the data storage component.

Deployments

Overview

Upriver offers two deployment models that vary based on where components of the architecture are deployed. Generally, for the easiest integration and minimal over-head from the customer, the SaaS deployment is suggested. However, we also support a deployment mode in which component interacting with customer data can be deployed in the customer's environment to meet enhanced security and privacy needs.

SaaS Deployment

In this mode, all of Upriver's components are deployed in Upriver's cloud environment. Interaction with customer data is done via a read-only role created by in the client's environment and assumed by Upriver's cloud service.

Hybrid Deployment

Upriver's cloud service resides in Upriver's environment, but the entire data plane (metadata storage and data analyzer engine) resides in the customer's environment. This deployment insure that no data ever leaves the client environment.