Skip to main content

DataHive Migration for TCS Users

Trusted Center for Sensor Data (TCS) will transit to be a tenant within DataHive from 1st August 2024. All existing TCS integrations and endpoints will continue to work till 31st October 2024.

Existing TCS users may need to perform some migration actions.

Please see the following sections below to see what needs to be done.

TCS API Users​

Changes​

  • Switch API URL from https://api.tcs.gov.sg to https://api.datahive.gov.sg.
  • Ensure your calling system is able to resolve api.datahive.gov.sg to 10.192.185.68 (same IP as tcs.gov.sg).
    • If using WOG DNS resolver - No action required.
    • If using other DNS service - Add DNS record api.datahive.gov.sg and datahive.gov.sg to 10.192.185.68.
  • Obtain your API token from https://datahive.gov.sg.
  • Migrate all API calls from the Curation Job endpoints to the Query Job endpoints specified here by the cutoff date.

No Changes​

  • No changes to existing TCS API specifications until the cutoff date.

TCS Snowflake System Connection Users​

Changes​

  • Switch Snowflake URL from govtech-tcs.privatelink.snowflakecomputing.com to govtech-datahive.privatelink.snowflakecomputing.com.
  • Add DNS record: govtech-datahive.privatelink.snowflakecomputing.com to 10.192.185.164 (same IP as govtech-tcs.privatelink.snowflakecomputing.com)

No Changes​

  • No change for the system's service principal
  • No change to snowflake database/schema names

TCS Non-Government Entities / Third Party (NGE/3P) Users​

Changes​

No Changes​

  • No changes to API specification

Databricks Users​

Changes​

  • Change in catalog name from govtech_tcs to govtech_datahive.
  • Existing notebooks that references govtech_tcs will be updated by TCS to reference govtech_datahive automatically during the migration.