We have released new Storage-Optimized Droplet plans for MySQL and PostgreSQL with 48 CPUs, 384 GiB of RAM, and 20 TB (MySQL)/30 TB (PostgreSQL) of storage in SGP1, SFO2, and FRA1. For more details, see our pricing pages for MySQL and PostgreSQL.
All managed databases except MongoDB now support up to 2,000 IP addresses as trusted sources. To add trusted sources, see our guides for MySQL, PostgreSQL, Caching, MongoDB, OpenSearch, and Kafka.
PostgreSQL 17 is now available for database clusters. You can upgrade earlier versions of PostgreSQL clusters to newer versions without any downtime using the DigitalOcean Control Panel.
All Managed Databases are now available in NYC2.
PostgreSQL 12 is now deprecated. All existing PostgreSQL 12 database clusters are scheduled to automatically upgrade during the cluster’s upgrade window.
PostgreSQL clusters now support pgvector v0.7.2. You can verify your access to this feature by running \dx from psql or querying pg_extension and locating vector in the output. If you do not have access to this pgvector version yet, update your PostgreSQL cluster. For a full list of supported extensions, see our guide Supported PostgreSQL Extensions.
Managed databases now supports log forwarding to OpenSearch, Elasticsearch, and Rsyslog. You can create and manage log sinks using the control panel and DigitalOcean API. For more detailed steps, see our guides for MySQL, PostgreSQL, Redis, MongoDB, and Kafka.
You can no longer create new PostgreSQL 12 managed databases. However, you can still fork existing PostgreSQL 12 clusters until PostgreSQL 12’s end of life on 14 November 2024.
You can now view hundreds of new database metrics by accessing the metrics API endpoint. For more detailed steps, see our guides for MySQL, PostgreSQL, Redis, and Kafka.
You can now reconfigure MySQL, PostgreSQL, and Redis databases via the API, which lets you edit many database engine parameters that were previously unavailable for editing. For more detailed steps, see How to Reconfigure Database Clusters.
PostgreSQL 11 is now deprecated. All existing PostgreSQL 11 database clusters are scheduled to automatically upgrade to PostgreSQL 15 during the cluster’s upgrade window starting on 6 November 2023.
The following MySQL and PostgreSQL plans are now deprecated:
All of your existing database clusters with these plans are still functional and accessible to you. However, you cannot resize them. To regain access to these features, fork your database to a new cluster with a supported plan. For more detailed steps, see our guides on how to fork MySQL databases and fork PostgreSQL databases.
When creating or resizing MySQL or PostgreSQL clusters on DigitalOcean, you can now add additional storage independently from your chosen database configuration plan. This provides a more economic option for increasing storage, rather than upgrading your cluster’s entire plan.
For more details, see our guides on how to resize MySQL clusters and resize PostgreSQL clusters.
PostgreSQL clusters on DigitalOcean now support the pgvector extension, for vector similarity search. For a full list of supported extensions, see our guide Supported PostgreSQL Extensions.
PostgreSQL 15 is now available for database clusters. You can also now perform in-place upgrades for PostgreSQL clusters to newer versions without any downtime. We currently support PostgreSQL 12, 13, 14, and 15.
When creating a new Kubernetes cluster, you can add a free database operator (now in beta), which allows you to automatically link new databases to your cluster. For more details, see our guide.
In App Platform, you can now create bindable environment variables for your PostgreSQL database connection pools. For detailed instructions, see our reference page.
To improve security, DigitalOcean no longer accepts TLS 1.0 and TLS 1.1 connections. This includes connections to www.digitalocean.com, cloud.digitalocean.com, and api.digitalocean.com.
You can now configure your MySQL, PostgreSQL, and Redis managed databases by making a PATCH request to /v2/databases/{database_cluster_uuid}/config. For example:
{
"config": {
"sql_mode": "ANSI,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION,NO_ZERO_DATE,NO_ZERO_IN_DATE,STRICT_ALL_TABLES",
"sql_require_primary_key": true
}
}
For more details, see the full reference documentation for the managed databases API.
PostgreSQL 14 is now available for database clusters. You can upgrade earlier versions of PostgreSQL clusters to newer versions without any downtime using the DigitalOcean Control Panel.
The database online migration feature for the MySQL, PostgreSQL, and Redis database engines no longer supports migrating databases from clusters inside of DigitalOcean to other clusters inside of DigitalOcean.
Online migration is now available for the MySQL, PostgreSQL, and Redis database engines. Online migration allows you to migrate databases from external servers or cloud providers to databases in your DigitalOcean account.
All DigitalOcean databases now support App Platform apps as trusted sources, including MongoDB.
Released v1.63.0 of doctl, the official DigitalOcean CLI. This release includes a number of new features:
database firewall sub-commands now support apps as trusted sourcesmonitoring alert sub-commands for creating and managing alert policies--droplet-agent flag was added to the compute droplet create sub-command to optionally disable installing the agent for the Droplet web consolePostgreSQL 13 is now available for database clusters. You can also now perform in-place upgrades for PostgreSQL clusters to newer versions without any downtime. We currently support PostgreSQL 10, 11, 12, and 13.
You can now deploy managed databases on Droplets with dedicated CPUs for the PostgreSQL, MySQL, and Redis engines.
Online migration for PostgreSQL and Redis databases has been released in Beta. Select users can now migrate Redis and PostgreSQL databases that reside inside and outside of DigitalOcean to existing database clusters in their DigitalOcean account. Redis migrations from AWS ElasticCache are not currently supported.
PostgreSQL 12 is now available for database clusters. You can also now perform in-place upgrades for PostgreSQL clusters to newer versions without any downtime. We currently support PostgreSQL 10, 11, and 12.
The DigitalOcean Virtual Private Cloud (VPC) service is now available for all customers. VPC replaces the private networking service. Existing private networks will continue to function as normal but with the enhanced security and features of the VPC service. See the description of VPC features for more information.
We began the incremental release of the DigitalOcean Virtual Private Cloud (VPC) service. It will be available for all customers soon. VPC replaces the private networking service.
v1.13.0 of the DigitalOcean Terraform Provider is now available. This release adds support for tagging managed databases clusters.
Bandwidth billing for managed databases, originally slated to begin in January 2020, has been postponed to 2021. Egress bandwidth for managed databases clusters will continue to be waived until then.
Users can now use the DigitalOcean API to set and modify trusted sources for managed databases to restrict incoming connections.
DigitalOcean Managed Databases now support private networking. New database clusters will provision with private networking enabled. Existing clusters will require an update to connect over the private network.
Managed databases are now in General Availability. New features include enhanced monitoring insights, support for projects and tags, and availability in the Singapore (SGP1) region.
DigitalOcean Managed Databases were released with support for PostgreSQL v10 and v11.