Static IPs

Overview

Goldsky can connect to your sinks using static IPs. This is helpful if you want to further restrict access to your sinks and ensure that only Goldsky-owned services can reach them. It works the same way for Turbo and legacy Mirror pipelines. This feature is available for enterprise customers. Contact us at support@goldsky.com (or through Slack/Telegram) to request access to this feature, or schedule a call with our team.

Usage

Reach out to us to have this feature enabled for your account.
Allowlist the following IPs on your database or network firewall: 100.21.15.214, 44.229.26.196, 44.230.239.184, 52.38.124.121
Make sure you’re using the latest version of the CLI; see the installation guide.
Set use_dedicated_ip: true at the top level of your pipeline YAML and deploy.

Example Turbo pipeline:

name: private-ip-pipeline
resource_size: s
use_dedicated_ip: true # Route this pipeline's traffic through Goldsky's static egress IPs

sources:
  ethereum_erc20_transfers:
    type: dataset
    dataset_name: ethereum.erc20_transfers
    version: 1.2.0 # Dataset version
    start_at: latest

sinks:
  postgres_transfers:
    type: postgres
    from: ethereum_erc20_transfers
    schema: public
    table: erc20_transfers
    secret_name: DB_WITH_IP_ALLOWLISTED
    primary_key: id

Mirror pipelines use the same top-level use_dedicated_ip: true flag in their YAML (alongside Mirror’s required apiVersion: 3 field).

Without use_dedicated_ip: true, pipelines connect from dynamic IPs and an IP-restricted firewall will reject the connection.

Get started

Solutions

Account & billing

Security & operations

API reference

Resources

Overview

Usage

​Overview

​Usage

Overview

Usage