For AI agents: The documentation index is at https://docs.digitalocean.com/llms.txt. Markdown versions of pages use the same URL with index.html.md in place of the HTML page (for example, append index.html.md to the directory path instead of opening the HTML document).

Upcoming Changes

• DigitalOcean Managed Caching is being discontinued on 30 June 2025.

  To replace Managed Caching, we are offering Managed Valkey, a Redis-compatible alternative with RDMA and higher throughput. All existing Managed Caching clusters automatically convert to Valkey clusters by 30 June 2025 during your upgrade window, retaining all data.

June 2026

30 June

• DigitalOcean Managed Valkey database clusters now support custom CNAME records, allowing clients to connect through your own hostname instead of the default *.db.ondigitalocean.com address. Custom CNAMEs are available through the API when creating clusters or when updating an existing cluster, and apply to the public network connection only. For more information, see Configure Custom CNAMEs for Valkey.

May 2025

16 May

• New managed database clusters are now automatically provisioned with default alert policies for CPU, memory, and disk utilization at a 90% threshold. These alerts notify you via email when resource usage is high, so you can investigate your application load or scale your cluster. You can modify or remove the default alerts at any time. For more information, see the following:

  • How to Set Up Kafka Cluster Monitoring Alerts
  • How to Set Up MongoDB Cluster Monitoring Alerts
  • How to Set Up MySQL Cluster Monitoring Alerts
  • How to Set Up OpenSearch Cluster Monitoring Alerts
  • How to Set Up PostgreSQL Cluster Monitoring Alerts
  • How to Set Up Valkey Cluster Monitoring Alerts

7 May

• You can now manually convert your Caching cluster to a Valkey cluster. All Caching clusters automatically convert to Valkey clusters by the Managed Caching discontinuation date.