Supported Engines

CloudNexus provides optimized, enterprise-grade managed databases with automated backups, point-in-time recovery, and built-in encryption at rest and in transit.

Engine Latest Version Use Case HA Support
PostgreSQL 15.4 / 16.0 Relational, JSON, Geospatial ✅ Yes
MySQL 8.0 / 8.4 Web Apps, CMS, Legacy ✅ Yes
Redis 7.2 Caching, Sessions, Pub/Sub ✅ Cluster Mode
MongoDB 6.0 / 7.0 NoSQL, Document Storage ✅ Replica Set

Deployment Methods

Use the cx db create command to provision instances directly from your terminal. Ensure you have the CloudNexus CLI v3.2+ installed.

bash
cx db create \n  --name production-postgres \n  --engine postgresql \n  --version 15.4 \n  --plan pro-4 \n  --region us-east-1 \n  --vpc-id vpc-0a1b2c3d \n  --backup-retention 14d
ℹ️
Pro Tip: Add --wait to block until the instance reaches healthy status. Use --dry-run to validate configuration before provisioning.

Deploy through the CloudNexus Control Panel for visual configuration:

  1. Navigate to DatabasesCreate Instance
  2. Select your engine and version
  3. Configure compute tier, storage IOPS, and VPC peering
  4. Define backup schedule and encryption keys
  5. Click Provision and monitor deployment progress in real-time

Programmatically deploy using the CloudNexus REST API:

curl
curl -X POST https://api.cloudnexus.io/v1/databases \n  -H "Authorization: Bearer $CX_API_KEY" \n  -H "Content-Type: application/json" \n  -d '{
  "name": "staging-redis",
  "engine": "redis",
  "version": "7.2",
  "plan": "standard-2",
  "region": "eu-west-2",
  "auto_scaling": true,
  "max_connections": 1000
}'

Configuration & Environment

After deployment, access your database connection string and configure environment variables. All instances are provisioned with private endpoints by default.

env
DB_HOST=pg-primary.us-east-1.db.cloudnexus.io
DB_PORT=5432
DB_NAME=app_production
DB_USER=cx_admin
DB_PASSWORD=
DB_SSL_MODE=require
DB_POOL_SIZE=20

For Kubernetes deployments, inject credentials securely using CloudNexus Secrets Manager or HashiCorp Vault integration.

Security & Compliance

Every database instance is deployed with enterprise-grade security controls:

  • Encryption at Rest: AES-256 with customer-managed or CloudNexus-managed KMS keys
  • Encryption in Transit: TLS 1.3 enforced for all connections
  • Network Isolation: VPC peering, private subnets, and customizable security groups
  • Access Control: Role-based permissions, IP whitelisting, and automated credential rotation
  • Auditing: Full query logging, connection tracking, and SOC2/ISO27001 compliant logs
⚠️
Important: Public endpoints are disabled by default. Enable them only when explicitly required, and always restrict access by CIDR ranges. We recommend using SSL_MODE=verify-full for production workloads.

Next Steps