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:
- Production
- Staging
| User | Resource | IP | Protocol & Port(s) |
|---|---|---|---|
| Consumer & Provider | DataHive REST API Endpoint | 10.192.185.68 | tcp/443 |
| Consumer with Synchronous API (Enhanced) | DataHive Gateway | 10.192.185.132 | tcp/443 |
| Consumer | DataHive Snowflake Data Warehouse | 10.192.185.164 | tcp/443 |
| Consumer | DataHive Snowflake Internal Storage | 10.192.185.167 | tcp/443 |
| User | Resource | IP | Protocol & Port(s) |
|---|---|---|---|
| Consumer & Provider | DataHive REST API Endpoint | 10.192.189.70 | tcp/443 |
| Consumer with Synchronous API (Enhanced) | DataHive Gateway | 10.192.189.148 | tcp/443 |
| Consumer | DataHive Snowflake Data Warehouse | 10.192.189.164 | tcp/443 |
| Consumer | DataHive Snowflake Internal Storage | 10.192.189.165 | tcp/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.
If your system is connected to the WOG DNS then there is no need to add entries that are already in the WOG DNS.
- Production
- Staging
| User | Domain | IP | In WOG DNS |
|---|---|---|---|
| Consumer & Provider | datahive.gov.sg | 10.192.185.68 | Yes |
| Consumer & Provider | api.datahive.gov.sg | 10.192.185.68 | Yes |
| Consumer with Synchronous API (Enhanced) | gateway.datahive.gov.sg | 10.192.185.132 | Yes |
| Consumer | govtech-datahive.privatelink.snowflakecomputing.com | 10.192.185.164 | No |
| Consumer | 9cxpjxsfcb1stg.blob.core.windows.net | 10.192.185.167 | No |
| Consumer | 9cxpjxsfcb1stg.privatelink.blob.core.windows.net | 10.192.185.167 | No |
| User | Domain | IP | In WOG DNS |
|---|---|---|---|
| Consumer & Provider | stg.datahive.gov.sg | 10.192.189.70 | Yes |
| Consumer & Provider | api-stg.datahive.gov.sg | 10.192.189.70 | Yes |
| Consumer with Synchronous API (Enhanced) | gateway-stg.datahive.gov.sg | 10.192.189.148 | Yes |
| Consumer | govtech-datahive-stg.privatelink.snowflakecomputing.com | 10.192.189.164 | No |
| Consumer | by67dwsfcb1stg.blob.core.windows.net | 10.192.189.165 | No |
| Consumer | by67dwsfcb1stg.privatelink.blob.core.windows.net | 10.192.189.165 | No |
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
Only direct connection to Snowflake supports internet access.
In your system, please whitelist the following domains.
There is no fixed IP for Snowflake public endpoint. Please whitelist by domain instead.
- Production
- Staging
| User | Domain |
|---|---|
| Consumer | govtech-datahive.snowflakecomputing.com |
| Consumer | 9cxpjxsfcb1stg.blob.core.windows.net |
| User | Domain |
|---|---|
| Consumer | govtech-datahive-stg.snowflakecomputing.com |
| Consumer | by67dwsfcb1stg.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.