Luden
GuinsooLabGitHub
  • Welcome to Luden!
  • Quickstart
    • Deploying with Docker
    • Building from Source
    • Scaling Luden Server
  • Configuration
    • Configuration
    • Authorization
    • Destinations Conf
      • Snowflake
      • AWS S3
      • AWS RedShift
      • Postgres
      • Google BigQuery
      • MySQL
      • Clickhouse
      • Guinsoo
      • WebHook
    • Sources Conf
      • Synchronization Scheduling
      • Airbyte Based Sources
    • Sources Catelog
  • Features
    • JavaScript Transform
    • Destination Tags
    • Data Warehouses
    • Match Mode
    • Stream Mode
    • DBT Cloud Integration
    • Event Cache
    • Geo Data Resolution
    • Typecast
    • Admin Endpoint
    • Application Metrics
  • Sending Data
    • JS SDK
    • Node.js
    • Event API
    • Bulk API
    • Segment API
  • Extending
    • Destination Extensions
    • Source Extensions
    • API Specs
    • Luden Architecture
  • Appendix
    • Contribute
    • FAQs
Powered by GitBook
On this page
  1. Configuration
  2. Destinations Conf

AWS RedShift

PreviousAWS S3NextPostgres

Last updated 2 years ago

Luden supports as a destination. For more information about Redshift . Redshift destination can work in stream and batch modes. In stream mode Luden uses plain insert statements for storing data. In batch mode Luden writes incoming events in formatted file on the AWS S3 and uses to store data from AWS S3 files into Redshift.

Configuration

Redshift destination config consists of the following schema:

destinations:
  my_redshift:
    type: redshift
    datasource:
      host: redshift.amazonaws.com
      db: my-db
      port: 5439
      schema: myschema
      username: user
      password: pass
      parameters:
        connect_timeout: 300
    s3:
      access_key_id: abc123
      secret_access_key: secretabc123
      bucket: my-bucket
      region: us-west-1
      folder: my_redshift

Redshift
see docs
COPY command