Static IPs

​

Overview

Goldsky can connect to your sinks using static IPs. This can be helpful if you want to further restrict access to your sinks and ensure that only Goldsky owned services can access them.

This feature is currently in a closed beta and only available for our enterprise customers. Please contact us at support@goldsky.com (or through Slack/Telegram) to request access to this feature.

​

Usage

1. Reach out to us to have this feature enabled for your account.
2. Whitelist the following IPs: 100.21.15.214, 44.229.26.196, 44.230.239.184, 52.38.124.121
3. Make sure you’re using the latest version of the CLI: curl | sh
4. Deploy your pipelines with the flag for enabling static IPs by setting the dedicated_egress_ip: true|false in the YAML config of your pipeline

Example:

name: private-ip-pipeline
apiVersion: 3
resource_size: s
dedicated_egress_ip: true
sources:
  reward:
    type: subgraph_entity
    subgraphs:
      - name: rewards-subgraph
        version: 1.0.1
    name: reward_payout
transforms: {}
sinks:
  rewards_payout_sink:
    type: postgres
    table: reward_payout
    schema: rewards
    secret_name: DB_WITH_IP_WHITELISTED
    from: reward