đēIntegrations
Outlines the concept of Integrations in the Orchestra platform
What is an Integration?
An integration refers to the seamless connection between Orchestra and external tools or services utilized in your data pipelines. These integrations facilitate the smooth flow of data, allowing you to harness the full potential of your preferred tools without any hassle.
How to Use Integrations
Using integrations within Orchestra is intuitive and user-friendly. Once you've logged in, simply navigate to the integration section where you can effortlessly set up and manage your connections. With just a few clicks, you can establish a secure link between our platform and your desired external tool.
For specific instructions on how to connect to each integration refer to either the setup guide in the platform or you can explore the available integrations and their instructions in this documentation by clicking here.
Multiple Credentials
Orchestra supports multiple credentials for the same integration. This can be useful for a number of reasons:
Granular Access Control: Different tasks within your data pipeline may require varying levels of access to the integrated tool. By creating multiple credentials, you can tailor access permissions to specific tasks, ensuring that each component operates within its designated boundaries.
Testing and Development: During the development and testing phase of your data pipelines, having multiple credentials allows you to isolate and test individual components without impacting the overall workflow. This enhances the reliability and stability of your pipelines before they go into production.
Security and Compliance: In environments where strict security and compliance regulations apply, having multiple credentials adds an extra layer of security. You can assign credentials based on user roles, ensuring that only authorized personnel have access to sensitive data and operations.
Common Authentication Issues
Some errors are common across integrations when attempting to connect Orchestra to them:
"Request timed out" - This error tends to indicate that the service you are trying to connect to is behind a firewall. This is common for integrations that are deployed in a VPN or on a private network. To avoid this issue you must add the Orchestra IPs to your whitelist IP list. The Orchestra IPs are:
13.41.17.109
13.42.169.51
18.168.251.89
Last updated