Skip to content

Creating a YugabyteDB data service#

To create a YugabyteDB data service you need a service location. Creating a network resource is optional: if you do not create one, Ametnes manages network access for the location — a shared load balancer publishes the endpoints for the services deployed there — so you create the service and connect. Create your own only if you want to control exposure (see Network Access Resources).

A YugabyteDB service exposes three protocol endpoints:

Connection Protocol Default port Description
ysql PostgreSQL wire protocol 5433 Distributed SQL (YSQL)
ycql Cassandra Query Language 9042 Cassandra-compatible API (YCQL)
yedis Redis protocol 6379 Redis-compatible API (Yedis)

Create the yugabyte data service#

In the Ametnes Cloud console;

  1. Navigate to the Services left menu.
  2. Click New Service.
  3. Enter Name: YugabyteService.
  4. Select Kind: YugabyteDB Service.
  5. Select the Location: your data service location. Leave Network unset to let Ametnes manage it.
  6. Select the Setup Architecture (for example Starter for evaluation, or Small and above for a replication-factor-3 cluster).
  7. Set the Admin Password for the yugabyte user (optional — a password is generated when omitted).
  8. Click Create Service and wait for the status ready.
service.tf
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
resource "ametnes_service" "service" {
  name        = "YugabyteService"
  project     = ametnes_project.project.id
  location    = data.ametnes_location.location.id
  kind        = "service/yugabyte:2026.1"
  nodes       = 3
  capacity {
    storage = 20
  }
  config = {
    "architecture"   = "Small"
    "admin.password" = "change-me"
  }
}

output "service_connections" {
  value = ametnes_service.service.connections
}

Connect#

Use the connections returned by the service. The ysql connection is PostgreSQL-compatible, so any PostgreSQL client works:

psql "host=<ysql-host> port=<ysql-port> user=yugabyte dbname=initdb"

For the Cassandra-compatible API use ycqlsh against the ycql connection, and for the Redis-compatible API use redis-cli against the yedis connection.

Scale#

Choose a larger Setup Architecture to scale the cluster. Tiers from Small upwards run three masters (a quorum) and add tablet servers as the tier grows, raising CPU, memory, and storage per node. See the tier list in the console for the CPU, memory, and storage each architecture provides.

Next#