Monte Carlo uses a data collector to connect to data warehouses, data lakes and BI tools in order to extract metadata, logs and statistics. The data collector is deployed in Monte Carlo's secure AWS environment across our Fortune 500 clients to ensure a seamless deployment process and best-in-class customer support. This section outlines the architecture and key components of the data collector.

Architecture

The data collector architecture is optimized as seen below to ensure maximum security as we interact with your data.

ArchitectureArchitecture

Architecture

Deployment requirements

👍

You are all set!

Monte Carlo is a SaaS platform. We will take on deployment and management of the instance.

Components of the data collector

  1. A VPC along with public/private subnets and other networking components. This VPC contains all components of the data collector. All outbound communication is routed through a single Elastic IP.
  2. A lambda function to handle API calls.
  3. A lambda function that executes distributed collection jobs. It connects to data warehouses, data lakes and BI tools to collect metadata, logs and metrics. This information is streamed back to Monte Carlo’s cloud via a secure Kinesis stream (using HTTPS calls).
  4. An S3 bucket that contains configuration and any other data required during processing.
  5. SQS queues to handle events in data lake environments.

Did this page help you?