Tembo Cloud: Now available in a region close to you

Aug 13, 2024 • 2 min read

blog post hero image

Following customer demand, we’ve now added the ability to deploy Instances to different Regions in Tembo Cloud. This of course is to reduce latency, to keep your data close to where you do your compute, but also because you might have requirements around data residency.

With this update we’ve added support for US West (Oregon), Asia Pacific (Singapore) and Europe (Frankfurt), in addition to the already available US East 1 (N Virginia.) We soon plan to add support for all AWS Regions and other major cloud providers in time.

Deploying to Regions

When creating an Instance, you can pick a Region using the drop-down selector.

Pick a cloud region via the Tembo Cloud UI

After deploying an Instance, the Region cannot be changed.

API

When using the Tembo API, Providers and Regions are represented as Dataplanes. Dataplanes are where Instances are hosted. A Dataplane is uniquely identified by provider_id, region_id, and index. Here is a sample of a Dataplane returned by the Tembo Cloud API.

 {
    "index": "data-1",
    "provider_id": "aws",
    "provider_name": "AWS",
    "region": "us-east-1",
    "region_id": "use1",
    "region_name": "US East 1 (N. Virginia)"
  }

When you create an Instance, you may specify the Provider and Region using provider_id and region_id. Tembo decides which index to deploy your Instance into. By default, instances are deployed to aws, use1.

Some queries to Tembo’s APIs involve fetching private data from your Instance, for example Logs, Metrics, and Secrets. These queries go to the Dataplane API, which has a different domain name for each Dataplane. This model allows for more secure handling of sensitive information. Dataplane API domain names are structured like this: api.< index >.< region_id >.tembo.io, for example api.data-1.use1.tembo.io.

For more information, please check the interactive API documentation.

What’s next?

When providers other than AWS are supported, we will include the provider_id in the domain name for Providers other than AWS. Supporting other clouds is on our immediate roadmap where you can also upvote for clouds you want us to add.

In addition, Tembo Self Hosted is already available for you today on EKS, AKS and GKE bringing the full power of Tembo Cloud to your Kubernetes cluster.