Vintner
Plant a Vine

Databases

Managed relational databases — Aurora, Cloud SQL, Azure Database with engine selection and capacity.

Databases

The databases section configures managed relational database instances. Multiple databases can be added per vine, each with its own engine, version, and capacity settings.

Fields Per Database

FieldTypeDescription
NameText inputUnique per vine, lowercase, used in resource naming
EngineSelectProvider-specific engine (see below)
Engine VersionAuto-setDetermined by engine selection
Min CapacityNumberMinimum capacity (ACUs for Aurora, vCPUs for Cloud SQL)
Max CapacityNumberMaximum capacity for auto-scaling
PortNumberDatabase port (default: 5432 for PostgreSQL, 3306 for MySQL)
IAM AuthToggleEnable IAM-based database authentication (AWS only)

Engines by Provider

Aurora Serverless v2 — auto-scaling managed database

EngineVersionCapacity Unit
Aurora PostgreSQL16.6ACUs (0.5–128)
Aurora MySQL8.0ACUs (0.5–128)

Aurora Capacity Units (ACUs) scale automatically between min and max. Each ACU provides ~2 GiB of memory. At $0.14/ACU-hour, a 0.5–4 ACU database costs approximately $51–$408/month.

Cloud SQL — managed database instances

EngineVersionCapacity Unit
Cloud SQL PostgreSQL15vCPUs (1–96)
Cloud SQL MySQL8.0vCPUs (1–96)

Azure Database Flexible Server — managed database

EngineVersionCapacity Unit
Azure PostgreSQL16vCores (1–64)
Azure MySQL8.0vCores (1–64)

Adding Multiple Databases

Click "Add Database" to add another instance. Each database gets its own card in the form. The first database defaults to:

  • Name: primary
  • Engine: Aurora PostgreSQL (or equivalent)
  • Capacity: 0.5–4 ACUs

Common patterns:

  • Primary + Read Replica: One write database + one read-optimized database
  • Multi-service: Separate databases per microservice (e.g., users-db, orders-db)

After Provisioning

Once deployed, the database card in the vine detail Services tab shows:

  • Writer endpoint — primary connection string
  • Reader endpoint — read replica connection (Aurora only)
  • Master credentials — stored in Secrets Manager (ARN shown, copy button)
  • Status — ACTIVE, CREATING, or FAILED

IAM authentication (AWS) allows Kubernetes pods to authenticate to the database using their service account identity (IRSA) instead of username/password. This eliminates credential rotation. See Security Architecture.

On this page