DoubleCloud Managed Service for ClickHouse®

Yes. Loads can be distributed across DB hosts using sharding.

No, cross-AZ traffic is free for DoubleCloud users.

Yes, you can change the cluster’s configuration, including adjustments to storage. If your cluster is in a high availability configuration with replicas for each shard, you will not have any downtime as the cluster will update gradually, node by node.

Backups are automatically created each day for each shard and stored for seven days.

Yes. Each cluster/node has a port and endpoint that exposes metrics that you can collect and visualize in your tools.

We have encryption in transit using SSL and encryption at rest based on the filesystem level.

Yes

Managed Clickhouse data will be stored in the DoubleCloud account.

BYOA is a handy piece of functionality with DoubleCloud that gives you the ability to deploy managed ClickHouse and managed Apache Kafka in your AWS account.

That means all data, computations, backups, encryption keys and S3 buckets are deployed in the user’s AWS account and the user is responsible to cover these costs to AWS.

You’ll still have the same level of functionality on the DoubleCloud management console, including all existing features like monitoring, backups, patching, configuration, security and high availability handled by us.

All resources like virtual machines, disks, S3 and traffic that’s provisioned and consumed is covered by users in AWS. DoubleCloud is providing automation of management Clickhouse and Apache Kafka as a service. That includes monitoring, backups, patching, configuration, security, high availability and load balancing, etc.

For the management part, DoubleCloud takes a management fee. To understand the price for BYOA, you’ll need to use a calculator at app.double.cloud and select the external network during the cluster’s configuration.

For more details of how to setup external network and activate BYOA see here.

We have two groups of resources that would be created in your account. In the first stage, we provision a new VPC, IAM role and VPC IPv6 CIDR Block.

These resources are created by adding external networks (BYOA) and launching a CloudFormation stack in your AWS account.

After that, DoubleCloud will be able to create resources only in that VPC under the role that was provided at the beginning.

In the second stage, virtual machines, disks, KMS keys and S3 buckets will be created when the user provisions a new cluster.

We provide the ability to deploy, modify, and manage all four of our services, including creating and deploying charts and dashboards via an API, which is available through the Python SDK, GO SDK or directly through gRPC.