Skip to content

Latest commit

Β 

History

History
108 lines (86 loc) Β· 5.95 KB

File metadata and controls

108 lines (86 loc) Β· 5.95 KB

import RESTPrereqs from "versionContent/_partials/_prereqs-cloud-account-only.mdx"; import CLIINSTALL from "versionContent/_partials/_devops-cli-install.mdx"; import CLIREF from "versionContent/_partials/_devops-cli-reference.mdx"; import NotSupportedAzure from "versionContent/_partials/_not-supported-for-azure.mdx";

$CLI_LONG is a command-line interface that you use to manage $CLOUD_LONG resources including VPCs, services, read replicas, and related infrastructure. $CLI_LONG calls $REST_LONG to communicate with $CLOUD_LONG.

This page shows you how to install and set up secure authentication for $CLI_LONG, then create your first service.

Prerequisites

Install and configure $CLI_LONG

Create your first $SERVICE_LONG

Create a new $SERVICE_LONG using $CLI_LONG:

  1. Submit a $SERVICE_SHORT creation request

    By default, $CLI_LONG creates a $SERVICE_SHORT for you that matches your $PRICING_PLAN:

    • $FREE: shared CPU/memory and the time-series and ai capabilities
    • Paid $PRICING_PLAN: 0.5 CPU and 2 GB memory with the time-series capability
    tiger service create

    To control the $SERVICE_SHORT configuration, use the service create flags. For example, to create a free service if you are in a paid $PRICING_PLAN, call tiger service create --memory shared --cpu shared.

    $CLOUD_LONG creates a Development environment for you. That is, no delete protection, high-availability, spooling or read replication. You see something like:

     πŸš€ Creating service 'db-11111' (auto-generated name)...
     βœ… Service creation request accepted!
     πŸ“‹ Service ID: tgrservice 
     πŸ” Password saved to system keyring for automatic authentication
     🎯 Set service 'tgrservice' as default service.
     ⏳ Waiting for service to be ready (wait timeout: 30m0s)...
     πŸŽ‰ Service is ready and running!
    πŸ”Œ Run 'tiger db connect' to connect to your new service
    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
    β”‚     PROPERTY      β”‚                                              VALUE                                               β”‚
    β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
    β”‚ Service ID        β”‚ tgrservice                                                                                       β”‚
    β”‚ Name              β”‚ db-11111                                                                                         β”‚
    β”‚ Status            β”‚ READY                                                                                            β”‚
    β”‚ Type              β”‚ TIMESCALEDB                                                                                      β”‚
    β”‚ Region            β”‚ us-east-1                                                                                        β”‚
    β”‚ CPU               β”‚ 0.5 cores (500m)                                                                                 β”‚
    β”‚ Memory            β”‚ 2 GB                                                                                             β”‚
    β”‚ Direct Endpoint   β”‚ tgrservice.tgrproject.tsdb.cloud.timescale.com:39004                                             β”‚
    β”‚ Created           β”‚ 2025-10-20 20:33:46 UTC                                                                          β”‚
    β”‚ Connection String β”‚ postgresql://tsdbadmin@tgrservice.tgrproject.tsdb.cloud.timescale.com:0007/tsdb?sslmode=require β”‚
    β”‚ Console URL       β”‚ https://console.cloud.timescale.com/dashboard/services/tgrservice                                β”‚
    β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
    

    This $SERVICE_SHORT is set as default by the $CLI_SHORT.

  2. Check the $CLI_SHORT configuration

    tiger config show

    You see something like:

    api_url:     https://console.cloud.timescale.com/public/api/v1
    console_url: https://console.cloud.timescale.com
    gateway_url: https://console.cloud.timescale.com/api
    docs_mcp:       true
    docs_mcp_url:   https://mcp.tigerdata.com/docs
    project_id:  tgrproject
    service_id:  tgrservice
    output:      table
    analytics:   true
    password_storage: keyring
    debug:       false
    config_dir:  /Users/<username>/.config/tiger
    

And that is it, you are ready to use $CLI_LONG to manage your $SERVICE_SHORTs in $CLOUD_LONG.