Regardless of whether you choose to deploy Upsolver on your virtual private cloud or ours, Upsolver clusters read data from S3, process it in-memory and write back to the S3 bucket. We never store any of your data, but you can choose where our processing, serving and streaming clusters will reside.
Data storage is done only on your Amazon S3, but data processing is done on EC2 clusters residing in Upsolver's AWS account
Data never leaves your AWS account and Upsolver employees have no access to it. We'll remotely manage EC2 clusters in your account,
Prepare to be astounded by how easy it is to prepare your data streaming.
When deploying Upsolver on private VPC, it is deployed entirely in your AWS account. In this option, Upsolver is unable to access any of your data, and is restricted to managing compute clusters on your AWS account.
The Upsolver web interface (accessible via app.upsolver.com) is hosted on a public Amazon S3 bucket. It connects to the public Upsolver API, which redirects it to the private API that is hosted on your AWS account. The public API is unable to access any data in your account.
Upsolver creates two separate roles in your account:
You control who can access your account by defining allowed and disallowed IP addresses. You can choose to permit Upsolver’s support team to access your web UI instance for troubleshooting and configuration purposes.
In private VPC, Upsolver does not require any inbound internet access. The private API does require outbound internet access, used for the following:
Troubleshooting is done based on system logs and metrics. Upsolver support might ask for additional information or access, which the customer can choose to share but is not obligated to do so. Access can be granted and removed instantly by modifying the security group IPs.