Goal
Create a database with the right expectations for connectivity, health, and restore behavior.Prerequisites
- A healthy node if the deployment model requires one
- Application credentials planning
Workflow
Choosing an engine and size
- Pick the engine: PostgreSQL, MySQL, or Redis.
- Choose a size option for the database (CPU/memory/storage tier).
- Database creation is subject to your plan limit, so you may be prompted to upgrade if you are at the cap.
Provisioning lifecycle
A new database moves through provisioning before it reaches running. Wait for running and healthy state before wiring an application to it — connection details are stable once it settles.What the database detail flow exposes after creation
- Credentials and connection details
- Metrics, observability snapshot, and logs
- Backups, restore, clone, and pooler-related controls
Expected result
A managed database is provisioned and usable from the platform.
Related guides
Credentials, pooling, and usage expectations
Understand how to consume database connection details and what to assume about pooling and access patterns.
Back up and restore a database
Use the current S3-backed database backup and restore model with the correct operational expectations.
Managed database overview
How StackShift databases fit into the platform and how they differ from stack-hosted stateful services.