Data Services

Databases, caches, queues, and other managed data resources are Components
in SVIEW. You provision them from the Catalog and manage them inside your
Services. This article covers how to provision one, where to find its
connection details, and how to get direct access to it.

Before you start

You need a SVIEW role that allows you to add Components to the Service you
are working in. If the Add Component action is not available, see User
Profile and Roles.
Decide which Service the data service belongs to, and which Environment that
Service sits in.

Provision a data Service

Open the Service where you want to add the data service.
Click Add Component and open the Catalog.
Under Databases (or Streaming for Kafka and queues), select the type
you need — PostgreSQL, MySQL, Redis, Kafka, and so on.
Fill in the configuration — instance size, storage, region, and name.
Click Save. The platform provisions the resource.

Verify it worked

The Component appears in your Service, and its dashboard shows Status as
available once provisioning finishes. Larger instances can take several minutes.

The data Service dashboard

Each data service Component has a dashboard showing:

Status — whether the instance is available
Connection details — hostname, port, and database name
Configuration — the settings that control how this resource is
provisioned
Secrets — credentials injected into applications that use this service
Variables — connection-related variables available to linked applications

Connect an application to a data Service

See Attach to Your Application for how to inject connection
credentials into your application Component so it can reach the data service.

Request direct developer Access

Direct access to a database — for running queries, debugging, or migrations —
is not available by default. Request it through Access requests in SVIEW:

Go to Access requests.
Select the role you need for the database, for example read-only or write
access.
Submit the request. A teammate with approval rights, or CTO2B support,
approves it.
Once approved, follow Connect to a Database to establish the connection
via Teleport.

Access is time-limited and expires automatically.

Common issues

A Component fails to provision. Some service types need platform-side
enablement in your Environment before they can be created — ElasticSearch is
one example. If provisioning fails, raise a request in your Slack channel
naming the Environment and the Component type, and CTO2B will enable it and
confirm when you can retry. Do not change platform-level variables yourself.

Connection details are missing. Wait until the Component's Status shows
as available; connection details and secrets are populated when provisioning
completes.

What CTO2B manages

CTO2B manages the underlying infrastructure for every provisioned data service
— instance health, engine version patching, automated backups, and network
security. Your team manages schema, data, queries, and application connection
configuration.