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 or fork them. To regain access to these features, migrate your database to a new cluster with a supported plan. For more detailed steps, see our guides on how to migrate MySQL databases and migrate 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.
DigitalOcean Managed Databases now supports Apache Kafka in early availability. For more details, see our Kafka documentation and regional availability matrix.
We have reenabled the creation of new resources in SFO2 for all customers.
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.
MongoDB 6.0 is now available in the control panel and via the API. To upgrade your MongoDB cluster to version 6.0, see our guide on upgrading your database cluster
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.
Redis 7.0 is now available when creating new databases. You can no longer create Redis 6.0 clusters. On 5 November 2022, we will officially no longer support 6.0 and will automatically upgrade all existing clusters to 7.0, with no expected downtime or interruptions.
In order 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.
MongoDB 5.0 is now available in the control panel and via the API. To upgrade your MongoDB cluster to version 5.0, see our guide on upgrading your database cluster
MongoDB clusters now support two Dedicated Droplet types: General Purpose and Memory-Optimized. If these options are available in your region, you can select them when creating a new cluster or resizing an existing one.
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.
MongoDB is now available as a managed database engine in the AMS3, BLR1, FRA1, LON1, NYC1, NYC3, SFO3, SGP1, and TOR1 regions.
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 consoleThe MongoDB database engine is now in general availability.
PostgreSQL 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.
Due to capacity limits in the region, we have disabled the creation of new resources in SFO2 for new customers. Existing customers with resources in SFO2 are unaffected and can still create and destroy resources in SFO2.
Redis 6 Managed Databases are now available. Redis 6 includes enhanced security features and client-side caching. You can no longer create Redis 5 clusters, but Redis 6 clusters are fully backwards compatible.
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.
You can now remove all global SQL modes from MySQL database clusters. Global SQL modes affect the SQL syntax MySQL supports and the data validation checks it performs.
Beginning 4 June 2020, you are required to create a primary key for each new table in any DigitalOcean Managed MySQL Database to improve cluster performance.
The SFO3 datacenter region is now available.
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.
Users can now set legacy MySQL 5x password encryption for MySQL 8+ Managed Databases from the control panel and API.
v1.13.0 of the DigitalOcean Terraform Provider is now available. This release adds support for tagging Managed Databases clusters.
Released v1.12.0 of the DigitalOcean Terraform Provider. This release contains improvements to Managed Database support including a new resource for configuring trusted sources and the ability to set the global SQL mode or Redis eviction policy on a cluster. There is also a new data source for finding supported Kubernetes versions. Learn more on the Terraform Changelog.
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.
MySQL managed database clusters now support setting the global SQL mode via the control panel and the API. See How to Set Global SQL Mode on MySQL Clusters for more information.
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.