Gas Station reference

This reference describes the configuration and deployment parameters for the Gas Station Service.

Before deploying the Gas Station Service, ensure you have:

• A running Ripple Custody environment
• Kubernetes cluster (1.21+)
• Helm (3.0+)
• PostgreSQL database (13+)

Configure the Gas Station Service using environment variables or Helm values:

Create a values file for the Gas Station Helm chart:

gasStation:
  enabled: true
  gatewayUrl: "https://your-custody-gateway.example.com"
  pollingIntervalMs: 5000
  maxRetryAttempts: 3
  retryIntervalMinutes: 5
  feeSafetyMarginPercent: 10
  
  database:
    host: "postgres.example.com"
    port: 5432
    name: "gas_station"
    username: "gas_station_user"
    existingSecret: "gas-station-db-credentials"
    
  credentials:
    existingSecret: "gas-station-credentials"
    privateKeyKey: "private-key"
    
  telemetry:
    enabled: true
    otlpEndpoint: "http://otel-collector:4317"

The Gas Station Service requires a PostgreSQL database for event deduplication and failed job tracking.

CREATE DATABASE gas_station;
CREATE USER gas_station_user WITH ENCRYPTED PASSWORD 'your-secure-password';
GRANT ALL PRIVILEGES ON DATABASE gas_station TO gas_station_user;

The service automatically creates the following tables on startup:

Serves as both event deduplication log and distributed lock mechanism. The UNIQUE constraint on id prevents duplicate event processing across multiple service instances.

Stores failed funding attempts for background retry processing.

Stores funding jobs that have permanently failed after exhausting all retry attempts.

• Store the bot user's private key in a secrets management solution (Kubernetes Secrets, HashiCorp Vault, AWS Secrets Manager)
• Never commit private keys to version control
• Rotate keys periodically according to your security policy

• Restrict database access to the Gas Station Service only
• Use network policies to limit communication between services
• Enable TLS for all connections (database, API gateway, telemetry)

• Enable audit logging in Ripple Custody to track all bot user actions
• Forward Gas Station logs to your SIEM for security monitoring
• Set up alerts for unusual funding patterns

The Gas Station Service exports metrics and traces via OpenTelemetry.

For telemetry configuration, see Telemetry overview.

The Gas Station Service exposes health check endpoints for Kubernetes liveness and readiness probes:

livenessProbe:
  httpGet:
    path: /health
    port: 8080
  initialDelaySeconds: 10
  periodSeconds: 30

readinessProbe:
  httpGet:
    path: /ready
    port: 8080
  initialDelaySeconds: 5
  periodSeconds: 10

These endpoints enable proper orchestration, zero-downtime deployments, and automatic service recovery.