Managed database connection service
Services/Cloud MySQL

Cloud MySQL service

Connection service for apps that use managed MySQL databases such as Amazon RDS instead of running MySQL inside the stack.

This service does not run the database server itself. It sits in the stack to hold connection settings, secrets, and service wiring for apps that should talk to a managed database.

Overview

Technical profile and packaging

This page shows how Cloud MySQL is packaged and versioned as a Wodby service, what it exposes at runtime, and which source artifacts it builds on.

Service type

Managed database connection service

Versions

5.5, 5.6, 5.7, 8

Labels

mysql

Stacks

Use it inside ready-made stacks or your own

These public stacks already include Cloud MySQL as part of their default service model. You can start there and customize the stack, or compose your own stack around the same building block.

Managed databases

Keep app-side database wiring in the service

Cloud MySQL is the connection layer between a stack and a managed database server. It keeps credentials, hostnames, and connection conventions attached to the platform workflow while the actual database runs outside the cluster.

Point the same stack at different providers

Use one provider in production and another in staging without rebuilding how the app connects to the database.

Keep connection details outside application code

Store database host, credentials, and related wiring in the platform instead of scattering them across codebases and environments.

Keep the database close to the cluster

When the stack runs on AWS EKS, Azure Kubernetes Service (AKS), DigitalOcean Kubernetes (DOKS), and Google Cloud Platform Kubernetes Engine (GKE), keep the managed database on the same cloud for faster connectivity and tighter security boundaries.