There are several setup tasks that may need to be completed by an administrator in your organization in order for your Coalesce account to be configured to work seamlessly within your larger data and technology infrastructure.
- 🔐 Authentication - Coalesce supports several authentication methods which can be mixed and matched according to your requirements and use cases. See the Security, Authentication Methods, Single Sign-On, and Users and sections of the Coalesce documentation for more information.
- 📝 Git configuration - Git integration is a core component of the Coalesce platform and must be configured, with access provided to each of your Coalesce developers, to deploy your data projects to non-development environments. See the our article on Git configuration and connectivity for more information.
- 💻 Command Line Interface - If you wish to leverage Coalesce's command line interface (CLI) to complete deploys and/or refreshes, it will need to be installed on the machine or service where it will be used. More information on installation can be found in the CLI Setup section of the Coalesce documentation.
- ❄️ Snowflake : Coalesce connectivity - If your organization uses a firewall and/or network policies in Snowflake to limit connectivity, you will have to allow connectivity from the Coalesce Services to Snowflake* in order for your users to be to connect to your Snowflake account within Coalesce. The Warehouse Whitelisting section of the Coalesce documentation details which IPs must be whitelisted.
- 📤 Outbound connectivity - If your organization limits outbound traffic to the public internet, you will need to allow outbound HTTPS connectivity on your network to several domains* in order to use the Coalesce user interface (UI), API, and/or CLI. The Allow Traffic to Coalesce Services section of the Coalesce documentation details which domains must be allowed.
* These requirements assume the traditional Coalesce connectivity approach is being leveraged. If you are using Coalesce with AWS PrivateLink or Azure Private Link, these requirements may not be required. Interested in learning more about our AWS PrivateLink / Azure Private Link capabilities? Contact Us for more information.