Skip to main content

Connection Setup

Intranet Connection Setup​

1. Firewall Rule Change Request​

Create Firewall Rule Change Request to open agency's client subnet to DataHive IPs. You can find some samples of such service request in here.

The DataHive IPs are as follows:

UserResourceIPProtocol & Port(s)
Consumer & ProviderDataHive REST API Endpoint10.192.185.68tcp/443
Consumer with Synchronous API (Enhanced)DataHive Gateway10.192.185.132tcp/443
ConsumerDataHive Snowflake Data Warehouse10.192.185.164tcp/443
ConsumerDataHive Snowflake Internal Storage10.192.185.167tcp/443
Setup verification

You can test this by using the netcat command. For example, nc -v -z 10.192.185.68 443 would return a success message.

2. Create DNS Entries​

Create DNS entries to allow your system(s) to resolve the IPs of DataHive's domains, you would need to add the following DNS entries to your appropriate DNS.

note

If your system is connected to the WOG DNS then there is no need to add entries that are already in the WOG DNS.

UserDomainIPIn WOG DNS
Consumer & Providerdatahive.gov.sg10.192.185.68Yes
Consumer & Providerapi.datahive.gov.sg10.192.185.68Yes
Consumer with Synchronous API (Enhanced)gateway.datahive.gov.sg10.192.185.132Yes
Consumergovtech-datahive.privatelink.snowflakecomputing.com10.192.185.164No
Consumer9cxpjxsfcb1stg.blob.core.windows.net10.192.185.167No
Consumer9cxpjxsfcb1stg.privatelink.blob.core.windows.net10.192.185.167No
Setup verification

You can test this by using the nslookup command.

For example, nslookup api.datahive.gov.sg would return an address of 10.192.185.68.

3. Testing your entire setup​

Your system should be able to connect to DataHive now.

For authentication, please refer to the documentation here. You may also attempt to implement and adapt from the sample scripts here.

For common errors, see FAQ

Internet Connection Setup​

warning

Only direct connection to Snowflake supports internet access.

In your system, please whitelist the following domains.

info

There is no fixed IP for Snowflake public endpoint. Please whitelist by domain instead.

UserDomain
Consumergovtech-datahive.snowflakecomputing.com
Consumer9cxpjxsfcb1stg.blob.core.windows.net
Setup verification

You can test this by using the curl command.

For example, curl -v https://govtech-datahive.snowflakecomputing.com. The endpoint should be responsive.