AWS
Upriver supports monitoring data sources in AWS in both SaaS and hybrid deployment models. Explanation regarding how to set up your environment is provided in this page. In either case, Upriver will provide you with a cloud formation script to run to set up your environment for working with Upriver.
To start setting up your environment, please contract an Upriver representative for an up to date cloud formation script.
SaaS
In a SaaS deployment a read only role is created, and Upriver is granted access to assume this role. This read role is then granted read access to any resource you wish to monitor using Upriver.
This process of creating this role is automated using a cloud formation script provided by Upriver.
After running the cloud formation you'll need to provide it's outputs to an Upriver representative, who will do the final setup for your account.
Cloud Formation Example:
Hybrid/Outpost
In a hybrid/outpost deployment, Upriver will create a Databricks workspace in your AWS account to run the monitoring from. Databricks will create a bucket, roles and compute resources it needs for Upriver's monitoring to run. In order to create this workspace multiple roles will be created to allow Upriver's Databricks to create and manage a workspace on your account.
In addition, a read role will be created just like in SaaS deployment. However, Upriver will only be able to assume the read role from the Databricks workspace in your account, and won't have permissions to assume it otherwise.
In a hybrid deployment - the databricks workspace will be created in dedicated AWS account you'll create for Upriver. Upriver will only have write/delete permissions for the dedicated account (provided via dedicated.yml) , and only have read permissions on your main AWS account.
In an outpost deployment - the databricks workspace will be created in the same AWS account that is monitored. This removes the need for a dedicated AWS account for Upriver, however requires providing Upriver write/delete permissions in your main account. As such, it is recommend to use a dedicated account if possible.
After running the cloud formation you'll need to provide it's outputs to an Upriver representative, who will create the Databricks workspace and do the final setup for your account.
Cloud Formation Example (hybrid setup + s3 bucket):
Last updated