> ## Documentation Index
> Fetch the complete documentation index at: https://www.aptible.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Managed Databases

> Fully managed, dedicated database instances: provisioning, scaling, backups, and encryption handled automatically.

![Databases Overview](https://mintcdn.com/aptible/nHu__nJZoe7eO21-/images/Databases---Overview.png?fit=max\&auto=format\&n=nHu__nJZoe7eO21-\&q=85\&s=5e62670e63aeeeb1d79980e5d04ccbaa)

## What is an Aptible Database?

An Aptible Database is a dedicated database instance, managed by the Aptible team. Aptible handles provisioning, scaling, in-place upgrades, backups, replication, network isolation, and encryption automatically.

The Aptible SRE team monitors every Database 24/7. Reliability practices include:

* Restarting a Database only for its own benefit -- to resolve or avoid an availability issue, or respond to a critical security incident -- not on a fixed schedule
* Automatically restarting containers that exit or run out of memory, and investigating the root cause of restart loops
* Monitoring disk usage and proactively scaling a Database before it runs out of space
* Keeping Database replicas distributed across Availability Zones, migrating back after any temporary exception

See [Reliability](https://www.aptible.com/docs/core-concepts/reliability/division-of-responsibility.md) for more detail.

> [!NOTE]
>
> Custom Databases are not supported.

## Explore Supported Database Types

> [card] [Elasticsearch](https://www.aptible.com/docs/elasticsearch.md)

> [card] [InfluxDB](https://www.aptible.com/docs/influxdb.md)

> [card] [MySQL](https://www.aptible.com/docs/mysql.md)

> [card] [PostgreSQL](https://www.aptible.com/docs/postgresql.md)

> [card] [RabbitMQ](https://www.aptible.com/docs/rabbitmq.md)

> [card] [Redis](https://www.aptible.com/docs/redis.md)

> [card] [SFTP](https://www.aptible.com/docs/sftp.md)

> [card] [See all](https://www.aptible.com/docs/core-concepts/managed-databases/supported-databases/overview)

## Provisioning

Provision a Database from the Dashboard, the [Aptible CLI](https://www.aptible.com/docs/reference/aptible-cli/overview.md) (`aptible db:create`), or [Terraform](https://www.aptible.com/docs/reference/terraform.md). See [Provisioning Databases](https://www.aptible.com/docs/core-concepts/managed-databases/provisioning-databases.md) for details and provisioning-method-specific notes.

## Connectivity

### Public/Private Access

Expose a Database to the public internet or your Stack's internal network with a [Database Endpoint](https://www.aptible.com/docs/core-concepts/managed-databases/connecting-databases/database-endpoints.md). IP Filtering is strongly recommended for any Endpoint exposed publicly.

### Ephemeral Access

For ad-hoc access from your workstation, open a [Database Tunnel](https://www.aptible.com/docs/core-concepts/managed-databases/connecting-databases/database-tunnels.md), a temporary local connection that lasts up to 24 hours.

## Scaling

### Container Scaling

Scale vertically by adjusting CPU/RAM. You also have access to Aptible's [Container Profiles](https://www.aptible.com/docs/core-concepts/scaling/container-profiles.md) to modify the CPU/RAM ratio.

> [!NOTE]
>
> Aptible migrates Apps across Availability Zones automatically, but Database scaling [can be blocked](https://www.aptible.com/docs/core-concepts/scaling/container-profiles.md#supported-availability-zones) if the target AZ doesn't support the desired Container Profile. Resolving this requires a full disk backup and restore.

### Disk & Throughput (IOPS) Scaling

Database disks can only be scaled up to 16,384GB. Disk can be scaled per database up to once a day and cannot be scaled down. IOPS and throughput can be tuned separately. See [Database Scaling](https://www.aptible.com/docs/core-concepts/scaling/database-scaling.md) and [Database Performance Tuning](https://www.aptible.com/docs/core-concepts/managed-databases/managing-databases/database-tuning.md) for details.

## High Availability

Databases don't scale horizontally by adding containers to the same instance. High availability instead comes from [Replication and Clustering](https://www.aptible.com/docs/core-concepts/managed-databases/managing-databases/replication-clustering.md) (Production and Enterprise plans), which deploys replicas across separate Availability Zones automatically. Support varies by engine: PostgreSQL and MySQL support read replicas, Redis supports read-only replicas, and MongoDB supports replica sets.

## Backups and Data Protection

Aptible takes automated daily backups of every Database, with configurable retention, manual backups, and cross-region backup copies. See [Database Backups](https://www.aptible.com/docs/core-concepts/managed-databases/managing-databases/database-backups.md). PostgreSQL 13+ Databases also support [Point-in-Time Recovery](https://www.aptible.com/docs/core-concepts/managed-databases/managing-databases/point-in-time-recovery.md), restoring to any point covered by your backup retention window.

## Encryption

Databases are encrypted at rest by default, with encryption in transit available via SSL/TLS. For key rotation or field-level control, Aptible also supports bringing your own AWS KMS key and application-level encryption. See [Database Encryption](https://www.aptible.com/docs/core-concepts/managed-databases/managing-databases/database-encryption/overview.md) for all available options.

## Learn more using Databases on Aptible

> [card] [Provisioning Databases](https://www.aptible.com/docs/provisioning-databases.md)
>
> Learn how to provision secure, fully Managed Databases

> [card] [Connecting to Database](https://www.aptible.com/docs/connecting-to-databases.md)
>
> Learn how to connect to your Apps, your team, or the internet to your Databases

> [card] [Managing Databases](https://www.aptible.com/docs/managing-databases.md)
>
> Learn how to scale, upgrade, backup, restore, or replicate your Databases