Skip to main content

VPC Deployment

Datacoves is designed to work on Public or Private Virtual Clouds. The following diagram shows the main services required by Datacoves when deployed on a VPC.

Datacoves Architecture​

Datacoves Architecture

Dependencies​

Datacoves can be deployed on AWS, Azure or Google Cloud.

Here is the list of services required, each cloud provider offers the service with a different name/brand.

ServicePurposeRequirementsQuantity
DatabaseDatacoves core servicesPostgreSQL > v.14, Minimum 2vcpu, 16Gb memory (*)1 server
DatabaseDatacoves stack servicesPostgreSQL > v.14, Minimum 4vcpu, 32Gb memory (*)1 server
Blob storageDBT artifactsN/A1 bucket
Blob storageGrafana logsLifetime policy with 30 days retention1 bucket
Blob storageAirflow DAGsN/A1 bucket per Airflow instance
Blob storageAirbyte logsN/A1 bucket per Airbyte instance
Blob StorageAirflow logsN/A1 bucket per Airflow instance
OIDC providerDatacoves SSOOauth 2.0 OIDC compliant provider1 provider (optional)
Managed KubernetesRuns the platform> v1.34Clusters are a minimum of 4 servers, sizing varies
Git serverDBT development version control> v2.331 server, or github/gitlab/etc.
CI/CD serverDBT developmentN/A1 server, or github/gitlab/etc.
HTTPS CertificateSecurityN/ATwo certificates are needed; datacoves.yourdomain.com and *.datacoves.yourdomain.com. Certbot is supported.
DNS EntriesHost ResolutionN/AExact configuration varies per cloud provider

(*) min. requirements may vary depending on the number of environments. For smaller installations, only one database server is needed.

Optional dependencies​

ServicePurposeRequirementsQuantity
Docker RegistryDocker images registryAny docker API compliant image registry1 service account
SMTP accountAirflow notificationsN/A1 service account
Slack accountAirflow notificationsN/A1 account
MS Teams accountAirflow notificationsN/A1 account