Deployment & Connecting to Resources

Review Platform Architecture & Deployment Options for details on selecting the right deployment model. Each section below details how to deploy on the various models.

Cloud Deployment

Simply follow the guide that is relevant to the integration you wish to connect:

See Network Connectivity to Resources if any of your resources need to be IP Allowlisted.

Cloud with Customer-hosted Object Storage Deployment (AWS)

  1. Follow this guide to create and register an AWS (S3) Data Store.

  2. Add your integration(s) by following the relevant guide:

Cloud with Customer-hosted Object Storage Deployment (GCP)

  1. Follow this guide to create and register a GCP (GCS) Data Store.

  2. Add your integration(s) by following the relevant guide:

Cloud with Customer-hosted Object Storage Deployment (Azure)

  1. Follow this guide to create and register a Azure (Blob Storage) Data Store.

  2. Add your integration(s) by following the relevant guide:

Customer-hosted Agent & Object Storage Deployment (AWS)

  1. Follow this guide to deploy an Agent.
  2. Add your integration by following the relevant guide (see supported integrations here).

Customer-hosted Agent & Object Storage Deployment (GCP)

  1. Follow this guide to deploy an Agent.
  2. Add your integration by following the relevant guide (see supported integrations here).

Customer-hosted Agent & Object Storage Deployment (Azure)

  1. Follow this guide to deploy an Agent.
  2. Add your integration by following the relevant guide (see supported integrations here).

FAQs

What about other integrations like dbt core, Airflow, Alation, Atlan etc.?

These connections either leverage our developer toolkit or are managed by a 3rd party.

Please see the details under the "OTHER INTEGRATIONS" subsection in our docs.

How do I list all of my Data Stores or Remote Agents?

All data stores and agents are listed on the dashboard here and can also be retrieved via the montecarlo agents list command. See the reference guide here.

How do I remove a Data Store or Remote Agent?

A data store or remote agent can be deregistered with the montecarlo agents deregister agent command. See the reference guide here.

Note that deregistering either a data store or agent does not remove any resources you may have provisioned, and replacing either will mean previous data (history) will no longer be accessible unless migrated.

Importantly, jobs also might fail if you remove an agent or store without coordinating with our team. Please reach out to your Monte Carlo representative or support ([email protected]), and we'd be happy to help!