LaserData Cloud
Getting Started

Quick Start

Connect to your LaserData Cloud deployment in minutes

This guide walks you through connecting to an existing LaserData Cloud deployment using our pre-built Docker quickstart image.

Prerequisites

  • A running LaserData Cloud deployment
  • Docker installed on your machine
  • Your deployment credentials (found in the Credentials tab of the Console)

1. Create an Access Rule

Before connecting, allow your IP address to reach the deployment.

  1. Open the Access Rules tab in the Console
  2. Click Add Rule
  3. Enter your current IP address (or CIDR range)
  4. Save the rule

See Access Rules for details on protocol selection and CIDR configuration.

2. Pull the Quickstart Image

docker pull ghcr.io/laserdata/quickstart:latest

3. Run the Producer

docker run ghcr.io/laserdata/quickstart \
  /producer {DOMAIN} \
  -u {USERNAME} \
  -p {PASSWORD}

This starts a producer that pushes sample messages to a sample-stream stream and sample-topic topic.

4. Run the Consumer

In a separate terminal:

docker run ghcr.io/laserdata/quickstart \
  /consumer {DOMAIN} \
  -u {USERNAME} \
  -p {PASSWORD}

This consumes and displays messages from the stream in real time.

Connection Options

OptionDescription
-t, --token <TOKEN>Use a Personal Access Token instead of username/password
--transport <tcp|quic|http|ws>Transport protocol (default: tcp)
--no-tlsDisable TLS (local development only)
--messages-count <N>Number of messages to send or receive
--stream <NAME>Custom stream name
--topic <NAME>Custom topic name

Run /producer --help or /consumer --help inside the container for all available options.

Quick Start via API

If you prefer the API over the Console, you can spin up a Free-tier deployment with a single call using your API key:

curl -X POST https://api.laserdata.cloud/tenants/{tenant_id}/divisions/{division_id}/deployments/starter \
  -H "ld-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "cloud": "aws",
    "region": "us-east-1"
  }'

cloud and region are required. You can optionally pass environment_name, environment_id, or deployment_name. See Create a Starter Deployment for the full reference.

On this page