Overview
This topic covers the prerequisites, network requirements, and cloud-side configuration needed to use Continuous Data for PaaS. It is intended to be shared with infrastructure and cloud platform teams to prepare the environment before DCT configuration begins.
Supported platforms
CD4P is delivered through two platform plugins: AWS Relational Database Service (RDS) and Azure SQL Managed Instance. The plugin determines which database types are available. Within the AWS RDS plugin, both Oracle (Multi-Tenant) and PostgreSQL are supported. The table below lists the supported database types per plugin.
-
AWS RDS Oracle: Multi-Tenant architecture only.
-
AWS RDS PostgreSQL: Manages the full RDS instance.
-
Azure SQL Managed Instance: Individual databases within a Managed Instance are managed as separate PaaS DBs.
General requirements
-
DCT must be able to reach cloud provider APIs over HTTPS. Ensure outbound connectivity from the DCT deployment to AWS or Azure API endpoints.
-
All PaaS resources managed by DCT must reside in the same cloud region. Cross-region operations are not supported.
-
A connected Continuous Compliance engine is required for profiling and masking workflows.
Architecture
DCT communicates directly with cloud provider APIs and, in some cases, with the PaaS databases themselves — for example, in the case of Azure SQL Managed Instance. The following placement guidelines apply:
-
DCT should be placed in a neutral network zone with HTTPS connectivity to both production and non-production cloud accounts.
-
The Continuous Compliance engine should be placed within the production zone or a zone with JDBC access to the production PaaS database. It needs direct database connectivity for profiling and masking.
-
Non-production PaaS databases do not require direct access to the Compliance engine after masking is complete.