Release Notes

Release notes track incremental improvements and major releases for the DigitalOcean cloud platform.

September 2021

September 28

  • Team members with the biller role no longer have view-only access to a team’s shared resources. Billers have full access to billing information only and no access to shared resources or team settings.

September 27

  • Debian 11.0 base image is now available in the control panel and via the API.

September 24

  • v2.12.1 of the DigitalOcean Terraform Provider is now available. This release adds CORS support for apps on App Platform and the ability to create monitoring alerts.

September 22

  • App Platform is now available in TOR1 and LON1.

September 21

September 1

  • We have begun charging a 7% Value Added Tax (VAT) to customers in Thailand. This VAT rate is temporarily reduced until 30 September 2021. Unless the TRD extends the temporary reduction, the rate will increase back to the standard VAT rate of 10% on 1 October 2021.

August 2021

August 31

August 20

  • Released v1.64.0 of doctl, the official DigitalOcean CLI. This release includes support for managing App Platform alerts.

August 18

August 9

  • 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:

    • The database firewall sub-commands now support apps as trusted sources
    • New monitoring alert sub-commands for creating and managing alert policies
    • The --droplet-agent flag was added to the compute droplet create sub-command to optionally disable installing the agent for the Droplet web console

  • The Droplet Console is now in General Availability.

August 5

August 3

August 2

  • CentOS Linux is reaching end of life; CentOS Linux 8 reaches EOL at the end of 2021 and there will be no CentOS Linux 9. As potential replacements, we have released two new Linux distributions for Droplets: CentOS Stream 8 (centos-stream-8-x64) and Rocky Linux 8.4 x64 (rockylinux-8-x64).

  • When updating an SSH key’s name using the API, if the request body does not contain a new name, the SSH key’s name will now retain its previous value. Previously, if the request body did not contain a new name, the SSH key’s name would update to a default value of either the comment field or the first 23 characters from the public key.

July 2021

July 9

  • Released v1.62.0 of doctl, the official DigitalOcean CLI. This release fixes a handful of bugs and introduces new flags on existing commands:

    • The apps logs command now supports tailing live logs with the --tail flag. This lets application owners select the most recent logs from their applications
    • The --wait flag was added to apps create and apps update to block these commands until an application is fully created or updated

June 2021

June 29

  • v2.10.0 of the DigitalOcean Terraform Provider is now available. This release adds support for Kubernetes maintenance policies.

  • v2.10.1 of the DigitalOcean Terraform Provider is now available. This release adds bug fixes and other improvements.

June 28

  • The MongoDB database engine is now in general availability.

  • The Ubuntu 16.04 and Fedora 32 images have been removed from the API.

June 25

June 10

  • The new Droplet Console is now in private beta. The Droplet Console gives you one-click SSH access to your Droplet from within a web browser, so you don’t need a password or SSH keys to connect.

June 2

  • A new Python + NodeJS group buildpack was added. Python apps can now use NodeJS to render assets during build or as a dependency at runtime.

May 2021

May 27

  • 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.

  • v2.7.0 of the DigitalOcean Terraform Provider is now available. This release adds support for distributing images to multiple regions.

May 26

  • Fedora 32 has reached its end of life. Per our image deprecation policy, you can now only deploy the Fedora 32 image via the API. We will remove the Fedora 32 image from the platform on 26 June 2021.

  • Ubuntu 16.04 has reached its end of life. Per our image deprecation policy, you can now only deploy the Ubuntu 16.04 image via the API. We will remove the Ubuntu 16.04 image from the platform on 26 June 2021.

May 17

  • Storage-Optimized Droplets are now available in SGP1.

May 6

  • Released v1.60.0 of doctl, the official DigitalOcean CLI. This release introduces an auth remove sub-command to simplify removing an auth context when managing multiple accounts. The databases user reset sub-command now supports resetting the user password for all database engine types.

May 5

  • We have updated the Floating IP API responses to better align with our newer API models. The droplet and region fields now use the same response models used in the /v2/droplets and /v2/regions endpoints. Specifically:

    • The private_networking feature is now displayed under the features field under droplet instead of the features field under region.
    • The vpc_uuid field now populates with the correct values.
    • The Droplet’s type displays base when the Droplet uses a base image (i.e. Ubuntu, CentOS).
    • The Droplet’s networks field now includes private and floating IP addresses, if applicable.

    Example Response:

    {
      "floating_ips": [
        {
          "ip": "144.126.248.39",
          "droplet": {
            "id": 228430424,
            "name": "ubuntu-s-1vcpu-1gb-nyc3-01",
            "memory": 1024,
            "vcpus": 1,
            "disk": 25,
            "locked": false,
            "status": "active",
            "kernel": null,
            "created_at": "2021-01-26T16:55:51Z",
            "features": [
              "private_networking"
            ],
            ...
            "networks": {
              "v4": [
                {
                  "ip_address": "192.20.2.55",
                  "netmask": "255.255.0.0",
                  "gateway": "",
                  "type": "private"
                },
                {
                  "ip_address": "192.127.2.2",
                  "netmask": "255.255.240.0",
                  "gateway": "161.35.176.1",
                  "type": "public"
                }
              ],
              "v6": []
            },
            "region": {
              "name": "New York 3",
              "slug": "nyc3",
              "features": [
                "backups",
                "ipv6",
                "metadata",
                "install_agent",
                "storage",
                "image_transfer",
                "server_id",
                "management_networking"
              ],
              "available": true,
              "sizes": [
              ...
              ]
            },
            "tags": [],
            "vpc_uuid": "21e31e10-24c5-47ec-8ae6-98da22"
          },
          ...
    }
    

    We have truncated the response for readability.

April 2021

April 27

  • Premium AMD Droplets are now available in NYC1, SGP1, AMS3, BLR1, LON1, and TOR1. You can view the availability of all of our products by datacenter in the regional availability matrix.

  • Fedora 34 base image is now available in the control panel and via the API.

April 26

  • Ubuntu 21.04 base image is now available in the control panel and via the API.

April 13

  • Released v1.59.0 of doctl, the official DigitalOcean CLI. This release includes a new apps propose sub-command and improvements to the apps spec validate sub-command.

April 9

  • With the completion of datacenter work, we have re-enabled resizing between regular and premium Intel Droplets in NYC3 and SGP1.

April 1

  • To comply with new provincial requirements in Canada, we are now collecting Provincial Sales Tax (PST) at a rate of 7% for customers in British Columbia and 6% in Saskatchewan. For more details, see Canada tax information.

  • Tax collection for Kenya has begun. Charge will appear on the May invoice.

March 2021

March 30

  • You can now deploy managed databases on Droplets with dedicated CPUs for the PostgreSQL, MySQL, and Redis engines.

March 29

  • Released v1.58.0 of doctl, the official DigitalOcean CLI. This release adds a --wait flag to the apps create-deployment command which blocks until the deployment is complete. By default, the registry kubernetes-manifest now generates a manifest that applies the secret to all the namespaces in the Kubernetes cluster using the DOSecret operator.

  • v2.7.0 of the DigitalOcean Terraform Provider is now available. This release adds support for Kubernetes node pool taints and resizing load balancers.

March 18

  • You can now do the following on Kubernetes clusters:

    • Use surge upgrade when upgrading an existing cluster. Surge upgrade is enabled by default when you create a new cluster.

    • Move a Kubernetes cluster and its associated resources, such as Droplets, load balancers and block storage volumes, to a project using the DigitalOcean control panel or doctl command-line tool. You can also assign a project when you create a new cluster. If you do not specify a project, it gets assigned to the default project.

    • Delete resources, such as load balancers and block storage volumes, associated with a Kubernetes cluster using the DigitalOcean control panel, API or the doctl command-line tool.

March 16

March 10

  • v2.6.0 of the DigitalOcean Terraform Provider is now available. This release enables surge upgrades for Kubernetes clusters by default and adds a digitalocean_firewall data source.

March 9

  • Storage Optimized Droplets are now available in TOR1 and BLR1.

March 3

  • 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.

  • With the completion of the SGP1 capacity augmentation, we have re-enabled the creation of new Spaces in SGP1.

March 1

  • Fixed a bug with DigitalOcean Load Balancers that prevented outbound data transfer from Droplets from being added to bandwidth usage totals. Any inconsistencies will be updated on the April invoice.

February 2021

February 25

  • The PHP buildpack received some updates:

    • Support for PHP 8.x was added in addition to PHP 7.x. By default, App Platform will use PHP 7.x unless the app specifies a version requirement via Composer.
    • Support for Composer 2.x was added in addition to Composer 1.x. App Platform will use the same version of Composer that generated the app’s composer.lock file.

    For more information and configuration options, see the buildpack’s documentation page.

February 22

  • Our Basic Droplet plans now include Premium Intel and AMD Droplets, which have faster Intel and AMD CPUs and NVMe SSDs. Premium Intel plans are availabile in all regions, and Premium AMD plans are available in NYC3, SFO3, and FRA1.

    All users can create Premium Droplets, resize from Regular Intel Droplets to Premium Intel Droplets, and create Premium Droplets as worker nodes in Kubernetes clusters. Resizing between Regular Intel Droplets to Premium Intel Droplets is disabled in NYC3 and SGP1 until the end of March 2021.

  • Released v1.57.0 of doctl, the official DigitalOcean CLI. This release enables surge upgrades by default for newly created Kubernetes clusters and important bugfixes for App Platform logs and Kubernetes cascading deletes.

February 11

  • App Platform is now available in SGP1 and BLR1.

  • FreeBSD 12.1 has reached its end of life. Per our image deprecation policy, you can now only deploy the FreeBSD UFS and ZFS image via the API. We will remove the images from the platform on 11 March 2021.

February 10

  • Released v1.56.0 of doctl, the official DigitalOcean CLI. This release includes support for database firewalls management, Kubernetes cascading deletes, and installing Kubernetes 1-Clicks to existing clusters.

February 3

  • v2.5.0 of the DigitalOcean Terraform Provider is now available. This release adds a number of improvements to the the digitalocean_app resource including: support for images as a component source, support for job components, support for internal_ports for services, and support for wildcard domains.

February 1

  • Spaces are now available in SFO3.

January 2021

January 31

  • 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.

January 28

  • We’ve improved the account deactivation experience to more clearly guide users through the actions necessary to deactivate an account.

January 21

  • Released v1.55.0 of doctl, the official DigitalOcean CLI. This release adds Docker Hub and GitLab support to App Platform’s create and update commands.

    • App Platform now supports launching components from public DockerHub image sources.

January 19

  • v2.4.0 of the DigitalOcean Terraform Provider is now available. This release includes support for deployments from GitLab and app-wide environment variables for the digitalocean_app resource, bug fixes, and other improvements.

January 5

January 1

  • In response to the United Kingdom departing as a member state of the European Union, DigitalOcean has obtained a standalone UK VAT ID and continued charging and collecting VAT at a rate of 20% on its business-to-consumer sales in the UK. Business customers with a valid UK VAT ID are subject to the reverse charge mechanism.

December 2020

December 7

  • Load balancers now come in small, medium, and large sizes. The larger the load balancer, the more simultaneous connections and requests per second it can manage. Existing load balancers are now considered “small” load balancers and are unaffected by this change.

  • CentOS 6 has reached its end of life. Per our image deprecation policy, you can now only deploy the CentOS 6 image via the API. We will remove CentOS 6 from the platform on 7 January 2021.

  • Load balancers now come in small, medium, and large sizes. The larger the load balancer, the more simultaneous connections and requests per second it can manage. Existing load balancers are now considered “small” load balancers and are unaffected by this change.

    You can specify the size of a load balancer during its creation using the size field. The available size values are lb-small, lb-medium, or lb-large.

    Example request body:

    {
      "name": "example-lb-01",
      "region": "nyc3",
      "size": "lb-small",
      "forwarding_rules": [
        {
          "entry_protocol": "https",
          "entry_port": 444,
          "target_protocol": "https",
          "target_port": 443,
          "tls_passthrough": true
        }
      ],
      "health_check": {
        "protocol": "http",
        "port": 80,
        "path": "/",
        "check_interval_seconds": 10,
        "response_timeout_seconds": 5,
        "healthy_threshold": 5,
        "unhealthy_threshold": 3
      },
      "sticky_sessions": {
        "type": "none"
      }
      ]
    }
    

    Once you have created a load balancer, you can’t change its size.

December 4

  • Released v1.54.0 of doctl, the official DigitalOcean CLI. This release user confirmation before container registry garbage collection is started.

December 3

  • v2.3.0 of the DigitalOcean Terraform Provider is now available. This release includes support for configuring the size of a digitalocean_loadbalancer resource. OpenBSD binaries are now built and available for download.

December 1

  • Fixed a bug that intermittently caused blank control panel pages in certain GeoIP regions.

  • We recently replaced Standard Droplet plans with Basic Droplet plans. Today, we have deprecated Standard Droplet plans from the API for new users. Existing customers will retain grandfathered access to these plans. See the API changelog for a full list of deprecated plans.

    Starting today, new users will no longer have access to the deprecated Standard Droplet plans from the API as well. Existing customers will retain grandfathered access to these plans.

    This is the complete list of plans deprecated for new users:

    Class Slug vCPUs RAM Disk Transfer Monthly Price
    Standard 512mb 1 512 MB 20 GB 1 TB $5
    Standard 1gb 1 1 GB 30 GB 2 TB $10
    Standard 2gb 2 2 GB 40 GB 3 TB $20
    Standard 4gb 2 3 GB 60 GB 4 TB $40
    Standard 8gb 4 4 GB 80 GB 5 TB $80
    Standard 16gb 8 16 GB 160 GB 6 TB $160
    Standard 32gb 12 32 GB 320 GB 7 TB $320
    Standard 48gb 16 48 GB 480 GB 8 TB $480
    Standard 64gb 20 64 GB 640 GB 9 TB $640
    Standard 96gb 24 96 GB 960 GB 10 TB $960
    Standard s-1vcpu-3gb 1 3 GB 60 GB 3 TB $15
    Standard s-3vcpu-1gb 3 1 GB 60 GB 3 TB $15
    Standard s-6vcpu-16gb 6 16 GB 320 GB 6 TB $80
    Standard s-8vcpu-32gb 8 32 GB 640 GB 7 TB $160
    Standard s-12vcpu-48gb 12 48 GB 960 GB 8 TB $240
    Standard s-16vcpu-64gb 16 16 GB 1280 GB 9 TB $320
    Standard s-20vcpu-96gb 20 20 GB 1920 GB 10 TB $480
    Standard s-24vcpu-128gb 24 24 GB 2560 GB 11 TB $640
    Standard s-32vcpu-192gb 32 32 GB 3840 GB 12 TB $960
    High Memory m-16gb 2 16 GB 60 GB 5 TB $75
    High Memory m-32gb 4 32 GB 90 GB 5 TB $150
    High Memory m-64gb 8 64 GB 200 GB 5 TB $300
    High Memory m-128gb 16 128 GB 340 GB 5 TB $600
    High Memory m-224gb 32 224 GB 500 GB 5 TB $1100

    You can view Droplet plans, the resources they provide, and the size slug used to identify them programmatically by querying the /v2/sizes endpoint.

November 2020

November 24

  • Released v1.53.0 of doctl, the official DigitalOcean CLI. This release adds support for container registry garbage collection of untagged manifests.

  • Fedora 31 has reached its end of life. Per our image deprecation policy, you can now only deploy the Fedora 31 image via the API. We will remove the Fedora 31 image from the platform on 24 December 2020.

November 18

  • 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.

  • Droplet-related error messages now display on the Droplet’s History page in the control panel.

November 12

  • v2.2.0 of the DigitalOcean Terraform Provider is now available. This release adds a new digitalocean_ssh_keys data source and a digitalocean_custom_image resource.

November 10

  • We have reduced the prices of Memory-Optimized Droplets by about 11%. Existing Memory-Optimized Droplets will be charged at the lowered price from the month of November on, reflected in the December invoice.

  • We have released Storage-Optimized Droplet plans. Storage-Optimized Droplets have NVMe SSD storage and are best for extra-large databases, caches, and analytics workloads.

    All users can now create Storage-Optimized Droplets in AMS3, FRA1, LON1, NYC1, and SFO3 using the control panel, API, or CLI. The slugs for the new plans are so-2vcpu-16gb, so-4vcpu-32gb, so-16vcpu-64gb, so-24vcpu-128gb, and so-32vcpu-256gb.

  • Released v1.52.0 of doctl, the official DigitalOcean CLI. This release adds a --force-rebuild flag to doctl apps create-deployment.

  • Improved build caching for all App Platform build environments. Dependencies and other data are now cached and reused between builds to improve performance. Dockerfile builds continue to make use of Docker layer caching.

    The Hugo buildpack received some updates:

    • The default version has been upgraded to 0.78.0.
    • Added support for running Hugo as a Service component. The default and recommended behavior is to deploy it as a Static Site.
    • Removed the implicit build command—a build command is now required. Existing apps have had their specs automatically updated.

November 6

  • We have released a “Deploy to DigitalOcean” button for App Platform. You can now embed a button into your GitHub repo or website that allows users to deploy your app directly to DigitalOcean.

    We have also released a jobs feature for App Platform. The job feature allows you to run application code at a scheduled time.

  • v2.1.0 of the DigitalOcean Terraform Provider is now available. DigitalOcean Container Registry is now in general availability and requires a subscription plan. As a result, the digitalocean_container_registry resource now requires setting a subscription_tier_slug which is supported with this release.

November 4

  • FreeBSD 12.2 UFS and ZFS base images are now available in the control panel and via the API. The image slug for the UFS FreeBSD image freebsd-12-x64 has been replaced with freebsd-12-x64-ufs. We will support 12.1 for three months after the release date of 12.2, which is currently scheduled for January 31, 2021.

November 3

  • Released v1.51.0 of doctl, the official DigitalOcean CLI. This release add support for managing DigitalOcean Container Registry subscriptions.

November 2

October 2020

October 30

  • Released v1.50.0 of doctl, the official DigitalOcean CLI. This release incudes a number for new features and improvements. It includes new doctl apps sub-commands to retrieve information about App Platform pricing plan tiers, instance sizes, and regions. The doctl registry sub-command now supports managing garbage collection for container registries.

October 28

  • Released v1.49.0 of doctl, the official DigitalOcean CLI. This release incudes the ability to update the default VPC for a region, the ability to set an expiration time when downloading kubeconfig files, and more.

October 27

  • On Kubernetes 1.19 and later we now provision two fully-managed firewalls for each new Kubernetes cluster. One firewall manages the connection between worker nodes and control plane, and the other manages connections between worker nodes and the public internet.

  • Fedora 33 base image is now available in the control panel and via the API.

October 26

  • You can now change the default VPC network for a region. When you change the default VPC network for a region, the new default network will be automatically selected during applicable resource set ups unless otherwise specified.

  • Added support to App Platform for configuring internal service ports, as well as internal-only services that are not internet-accessible.

  • Added support to App Platform for configuring a catch-all document that can be used by static sites to rewrite all requests to pages that are not found, to the configured document. The catchall_document field is similar to error_document in that they both rewrite all requests to the specified document, and so they are mutually exclusive, only 1 can be set. Using catchall_document will result in 200 HTTP response codes for the rewritten requests, while error_document will result in 404 HTTP response codes.

October 22

  • Ubuntu 20.10 base image is now available in the control panel and via the API.

October 20

  • v2.0.0 of the DigitalOcean Terraform Provider is now available. This release uses v2.0.3 of the Terraform Plugin SDK and now only supports Terraform v0.12 and higher. It also includes a new digitalocean_records data source.

October 19

  • You can now update a VPC network to be the default VPC network for a region using the PUT /v2/vpcs/$VPC_ID and PATCH /v2/vpcs/$VPC_ID endpoints.

    For example:

    {
      "name": "renamed-new-vpc",
      "description": "A new description",
      "default": "true"
    }
    

    When you change the default VPC network for a region, all applicable resources are placed into the default VPC network unless otherwise specified during their creation.

October 15

  • Added support to App Platform services and static sites for configuring an ingress CORS policy.

  • Added support to App Platform for configuring custom wildcard domains.

October 14

October 13

  • v1.23.0 of the DigitalOcean Terraform Provider is now available. This release introduces a new digitalocean_app resource with support for DigitalOcean App Platform.

October 12

  • Added an App Platform the environment variable binding prefix _self that can be used to reference the current component without directly referencing it by component name.

October 9

  • Launched the App Platform jobs component type, with support for running containerized operations before, after, and on failure of deploys.

October 6

  • You can now apply taints to Kubernetes node pools using the DigitalOcean API. When you configure taints for a node pool, the taint automatically applies to all current nodes and any subsequently created nodes in the pool. For more information, see Kubernetes' documentation on taints and tolerations.

  • Released v1.48.0 of doctl, the official DigitalOcean CLI. This release promotes doctl apps commands with support for DigitalOcean App Platform to General Availability.

  • App Platform, our new platform as a service (PaaS) offering, is now in General Availability. Hook a GitHub repo to DigitalOcean and let App Platform automatically build and deploy your commits live to the cloud. Read the quickstart or try it now.

  • You can now apply taints to Kubernetes node pools. When you configure taints for a node pool, the taint automatically applies to all current nodes in the pool and any node you add to the pool thereafter. For more information about taints and tolerations, see Kubernetes' documentation.

    Additionally, we’ve added node taint support for our official clients, godo and doctl. Only versions of doctl 1.47.0 and godo 1.45.0 and above support persistent node pool taints.

    You can define taints during a pool’s creation by submitting a POST request to the /v2/kubernetes/clusters/<cluster-id>/node_pools and the /v2/kubernetes/clusters endpoints, or you can update existing pools by submitting a PUT request to the /v2/kubernetes/clusters/<cluster-id>/node_pools/<node-pool-id> endpoint. For example, this request body defines two taints for a node pool.

    {
      "name": "frontend",
      "size": 10,
      [...]
      "taints": [
        {
          "key": "priority",
          "value": "high",
          "effect": "NoSchedule",
        },
        {
          "key": "workloadKind",
          "value": "database",
          "effect": "NoExecute",
        }
      ]
    }
    

October 5

  • Released v1.47.0 of doctl, the official DigitalOcean CLI. This release adds support for setting Kubernetes node pool taints.

October 1

September 2020

September 30

  • We have updated capacity in FRA1 and have resumed the creation of Spaces in that region.

September 25

  • We have temporarily disabled the creation of new Spaces in SGP1 while we update capacity in this region.

September 16

September 8

  • Fedora 30 has reached its end of life. Per our image deprecation policy, you can now only deploy the Fedora 30 image via the API. We will remove the Fedora 30 image from the platform on 8 October 2020.

September 2

  • Standard Droplet plans have been replaced with Basic Droplet plans. We have added one new plan, s-8vcpu-16gb, and deprecated the following plans:

    • s-1vcpu-3gb
    • s-3vcpu-1gb
    • s-6vcpu-16gb
    • s-8vcpu-32gb
    • s-12vcpu-48gb
    • s-16vcpu-64gb
    • s-20vcpu-96gb
    • s-24vcpu-128gb
    • s-32vcpu-192gb

    These deprecated plans are now unavailable in the control panel, but you can still create Droplets with those plans using the API or doctl.

August 2020

August 20

  • Account security history now displays only the last 12 months of account events. If you need data from an earlier date, open a support ticket.

August 4

  • We have released a Droplet metadata endpoint which returns whether or not a Droplet is scheduled for a live migration. The impact of live migrations on Droplets is minimal, so users now only receive direct notifications for migrations that require us to power down a Droplet, which (except in emergencies) we send 7 days in advance.

July 2020

July 31

July 28

July 23

  • FreeBSD 11.4 UFS and ZFS base images are now available in the control panel and via the API.

July 22

  • Memory-Optimized Droplets are now in general availability and are available in the SFO3 and TOR1 datacenter regions.

  • We have reenabled the creation of Spaces in NYC3 now that the datacenter’s capacity upgrade is complete. The ability to create new Spaces in FRA1 remains disabled while we finish that datacenter capacity upgrade.

  • Released v1.46.0 of doctl, the official DigitalOcean CLI. This release includes support for install Kubernetes 1-Click Apps when creating a cluster, surge upgrade support for Kubernetes clusters, and more.

  • v1.22.0 of the DigitalOcean Terraform Provider is now available. This release includes auto_upgrade and surge_upgrade support for the digitalocean_kubernetes_cluster resource.

July 20

  • v1.21.0 of the DigitalOcean Terraform Provider is now available. This release includes the addition of https to the list of acceptable healthcheck protocols for the digitalocean_loadbalancer resource.

July 8

  • Load balancer health checks now support the HTTPS protocol. You can now configure load balancers to verify the health of your Droplets' HTTPS endpoints.

July 7

July 6

  • Load balancer health checks now support the HTTPS protocol. You can now configure load balancers to verify the health of your Droplets' HTTPS endpoints.

July 1

June 2020

June 16

June 15

  • v1.20.0 of the DigitalOcean Terraform Provider is now available. This release includes the addition of a digitalocean_tags data source and improvements to other tag-related resources.

June 10

  • Released v1.45.1 of doctl, the official DigitalOcean CLI. This release updates doctl’s Snap packaging that allow Snap users to log in to DigitalOcean Container Registry using the doctl registry login command. To grant access doctl access to your Docker configuration, run snap connect doctl:dot-docker.

June 9

  • We have temporarily disabled the creation of new Spaces in FRA1 and NYC3 while we update capacity in these regions. Learn more about Spaces in FRA1 and NYC3.

  • Listing records for a domain now supports filtering by both name and type using query parameters. For example, to only include A records for a domain, send a GET request to /v2/domains/$DOMAIN_NAME/records?type=ATo only include records matching sub.example.com, send a GET request to /v2/domains/$DOMAIN_NAME/records?name=sub.example.com. name must be a fully qualified record name. Both name and type may be used together to further filter the records returned.

  • The response body to POST requests creating multiple Droplets has been extended to include an actions link for each Droplet created. For example:

        "links": {
          "actions": [
            {
              "id": 24404896,
              "rel": "create",
              "href": "https://api.digitalocean.com/v2/actions/24404896"
            },
            {
              "id": 24404897,
              "rel": "create",
              "href": "https://api.digitalocean.com/v2/actions/24404897"
            }
          ]
        }
    

    These can be used to check the status of each individual Droplet create event rather than polling each Droplet.

June 5

June 3

  • v1.19.0 of the DigitalOcean Terraform Provider is now available. This release includes initial support the DigitalOcean Container Registry.

June 2

  • Released v1.44.0 of doctl, the official DigitalOcean CLI. This release includes support for specifying a non-default VPC when creating Droplets, load balancers, and Kubernetes clusters. It also adds the ability to set an expiration time for container registry credentials. This can be useful when calling doctl registry login as part of a CI/CD process. A new doctl 1-click list subcommand is now also available.

  • Released v1.45.0 of doctl, the official DigitalOcean CLI. This release includes new doctl kubernetes 1-click list and doctl compute droplet 1-click list subcommands.

June 1

May 2020

May 26

May 15

  • Users can now search for Marketplace apps directly from the Droplet Create page.

  • Unassigned floating IP charges will now appear on invoices. The first charge will appear on July 2020 invoices for all floating IPs that were not assigned to Droplets during the month of June.

  • The retention period for Droplet performance metrics has been decreased from 30 days to 14 days.

May 12

May 6

  • It is now possible to adjust the behavior of the OAuth authorization flow by specifying a prompt and/or max_auth_age query parameter:

    • The prompt query parameter can be used to specify how the authorizing user should be authenticated.
    • The max_auth_age query parameter can be used to determine a deadline (in seconds) after which a user must re-authenticate on the control panel.

    For more details, consult the OAuth documentation.

May 5

  • v1.18.0 of the DigitalOcean Terraform Provider is now available. This release includes support for the backend keepalive option for the load balancer resource and data source.

April 2020

April 29

April 28

  • 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.

  • Released v1.43.0 of doctl, the official DigitalOcean CLI. This release updates container registry features from beta to early access.

  • v1.17.0 of the DigitalOcean Terraform Provider is now available. This release includes bug fixes and new Spaces data sources.

  • Load balancers now allow you to set a keepalive option for target Droplets.

  • Fedora 32 base image is now available in the control panel and via the API.

  • DigitalOcean Load balancers now allow you to set a keepalive option for forwarding rules. Enabling this option allows the load balancer to use fewer active TCP connections to send and receive HTTP requests between the load balancer and your target Droplets.

April 23

  • Released v1.42.0 of doctl, the official DigitalOcean CLI. This release includes a number of small UI improvements and support for additional container registry beta features.

  • Ubuntu 20.04 LTS base image is now available in the control panel and via the API.

April 22

April 21

  • You can now choose a root password during Droplet creation rather than receiving an automatically-generated password via email.

April 14

  • v1.16.0 of the DigitalOcean Terraform Provider is now available. This release includes VPC support and expanded Spaces support.

  • The login page now provides quick access to your last-used login method.

April 10

  • Released v1.41.0 of doctl, the official DigitalOcean CLI. This release fixes the link to create a new API token when running doctl auth init.

April 7

  • 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.

  • Released v1.40.0 of doctl, the official DigitalOcean CLI. This release includes a support for VPCs and viewing billing history for an account.

  • Starting today, we have begun the incremental release of DigitalOcean VPC, including its API. VPCs (virtual private clouds) allow you to create virtual networks containing resources that can communicate with each other in full isolation using private IP addresses. The VPC service will be available for all customers soon. It replaces the existing private networking service.

    When enabled on your account, you will be able to create, configure, list, and delete custom VPCs as well as retrieve information about the resources assigned to them. For example, to create a new VPC, make a POST to the /v2/vpcs endpoint with a JSON body like:

    {
      "name": "staging-vpc",
      "description": "VPC for the staging environment"
      "region": "nyc1"
    }
    

    For the more details, see the full API reference documentation for DigitalOcean VPCs.

    Related Changes

    This release contains related functionality for a number of other DigitalOcean resources.

    When VPC is enabled on your account, the private_networking attribute previously used to enable private networking while creating a Droplet will now provision the Droplet inside of your account’s default VPC for the region. Use the new vpc_uuid attribute to specify a different VPC.

    Kubernetes clusters, load balancers, and database clusters will also be provisioned inside of your account’s default VPC for the region when enabled. To specify a non-default VPC, set the appropriate attribute in the JSON body of the create request:

    Resource Attribute
    Droplet vpc_uuid
    Kubernetes cluster vpc_uuid
    Load balancer vpc_uuid
    Database cluster private_networking_uuid

March 2020

March 21

  • Business customers in Iceland can now enter their VAT IDs on the billing page. This removes tax charges on future invoices. Learn more about Iceland taxes.

March 19

March 18

  • v1.15.0 of the DigitalOcean Terraform Provider is now available. This release includes new data sources for accessing information about DigitalOcean regions, images, and projects, a new resource for adding resources to projects not created via Terraform, and a number of other improvements.

  • Released v1.39.0 of doctl, the official DigitalOcean CLI. This release includes support for listing and retrieving invoices as well as expanded help output for all commands.

March 16

March 13

  • Users who create a 1-Click application can now access the instructions for their app by clicking the Get Started link next to their Droplet on the project homepage.

  • The sign-in experience has been redesigned to help streamline two-factor authentication workflows and enable special announcements.

March 12

  • You can now only rebuild Droplets from images that use an OS that resides in the same OS family as the Droplet being rebuilt. For example, a Droplet running Ubuntu 16 can be rebuilt from an image running Ubuntu 18, but it cannot be built from an image running Debian.

March 11

  • We have finished expanding the AMS3 datacenter to address capacity and load issues with Spaces in that region. As a result, we have reenabled the creation of new Spaces in AMS3. The allowance and rate limits on uploads to Spaces in AMS3 will stay in place to ensure high performance.

  • Users can now upload custom images using FTP URLs.

  • Debian 10.3 and 9.12 base images are now available in the control panel and via the API.

March 9

March 4

  • Users can now set legacy MySQL 5x password encryption for MySQL 8+ Managed Databases from the control panel and API.

  • The DigitalOcean managed databases API now supports configuring the user authentication plug-in for both new and existing MySQL users. This is useful when needing to connect to a MySQL 8.0 cluster using an application or older MySQL client that does not support the default caching_sha2_password authentication plug-in.

    For example, to create a new MySQL user using the mysql_native_password authentication plug-in, send a POST request to /v2/databases/$DATABASE_ID/users with a JSON body like:

    {
      "name": "php-app-01",
      "mysql_settings": {
        "auth_plugin": "mysql_native_password"
      }
    }
    

    For more details, see the full reference documentation for the managed databases API.

March 1

  • Tax collection for Iceland has begun. Charges will appear on the April invoice.

February 2020

February 24

  • We began the incremental release of a feature that allows users to destroy select resources associated with a Droplet when they destroy the Droplet.

February 12

  • We have renamed the Limited Availability (LA) product lifecycle stage to Early Availability (EA) to better represent the status of products in that stage. Products in Early Availability are fully functional but not yet production-ready, and may be enabled only for specific user groups as part of an incremental roll-out strategy.

February 6

  • To provide a better service for all customers we are introducing burst request rate limits to our public API. Now clients will be rate limited if they consume more than 5% of their total requests for an hour over a 1 minute period (going over 250 requests in a minute). This only affects clients making their requests in large bursts, clients that spread their requests over time will not be affected. Check the rate limits documentation for more information about it.

February 5

  • v1.14.0 of the DigitalOcean Terraform Provider is now available. This release includes a bug fix for projects containing many resources and exposes the Droplet IDs for individual nodes in Kubernetes clusters.

February 4

  • Released several improvements for seeking support, including a new support starting page that allows you to search DigitalOcean’s product documentation, Marketplace, and community tutorials from a single location.

  • Released v1.38.0 of doctl, the official DigitalOcean CLI. This release adds the ability to set Kubernetes node pool labels as well as support for deleting multiple Kubernetes clusters with a single command.

  • Our managed DigitalOcean Kubernetes product DOKS now supports setting Kubernetes labels on node pools. Once assigned, they will propagate to the associated pool nodes, both existing and new ones. This way, customers may reliably reference groups of nodes through label selectors that Kubernetes provides.

    Labels can be set on node pool API objects that are accessible on multiple endpoints. For instance, updating an existing node pool by the labels service=web and priority=high is done by submitting a PUT request to the /v2/kubernetes/clusters/<cluster ID>/node_pools/<node ID> endpoint with the following JSON body:

    {
      "name": "web",
      "count": 10,
      "labels": {
        "service": "web",
        "priority": "high"
      }
    }
    

    For details, see the available operations on the Kubernetes API.

January 2020

January 30

  • The following distributions have reached end of life. Their distribution images are now deprecated and will be removed from the control panel and API on 1 March 2020:

    • Ubuntu 19.04
    • FreeBSD 12.0
    • Fedora 28
    • Fedora 28 Atomic
    • Fedora 29

    If you need to use these distribution versions, you can create Droplets from a snapshot of a Droplet with that version or from a custom image.

January 27

  • v1.13.0 of the DigitalOcean Terraform Provider is now available. This release adds support for tagging Managed Databases clusters.

January 24

  • RancherOS 1.5.5 base image is now available in the control panel and via the API.

January 22

  • CentOS 8.1 base image is now available in the control panel and via the API.

January 14

  • Released v1.37.0 of doctl, the official DigitalOcean CLI. This release adds the ability to retrieve account balances.

January 13

  • Our API has been extended with a new endpoint enabling you to retrieve your account balance. For more information, see the balance endpoint in the API reference documentation.

  • Our API has been extended with a new endpoint enabling you to retrieve balance information for an account. To do so, make a GET request to /v2/customers/my/balance. The response will be a JSON body including your balance details. For example:

    {
      "month_to_date_balance": "23.44",
      "account_balance": "12.23",
      "month_to_date_usage": "11.21",
      "generated_at": "2019-07-09T15:01:12Z"
    }
    

    For all the details, see the balance endpoint in the full API reference documentation.

January 1

December 2019

December 19

  • 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.

  • Users can now specify the payment method and amount when making payments on the billing page.

December 18

  • Fedora 31 base image is now available in the control panel and via the API.

December 17

  • 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.

  • Debian 10.2 base image is now available in the control panel and via the API.

December 12

  • FreeBSD 12.1 (ufs & zfs) base image is now available in the control panel and via the API.

  • Our referral program offer has changed from $50 for 30 days to $100 for 60 days. This change applies only to new referrals. Existing users with referral credits will retain their current balance and credit expiration dates.

December 2

  • The DigitalOcean API currently offers the ability to retrieve a report of all Droplets co-located on the same physical hardware by sending a GET request to the /v2/reports/droplet_neighbors endpoint. This endpoint has been deprecated and will begin responding with an HTTP status of 410 (Gone) on December 17th, 2019.

    Today, in its place, a new endpoint is now available: /v2/reports/droplet_neighbors_ids. Rather than listing the full Droplet object, responses from this endpoint only contain sets of Droplet IDs co-located on the same physical hardware. For example:

    {
      "neighbor_ids": [
        [168671828,168663509,168671815],
        [168671883,168671750]
      ]
    }
    

    This implementation is more performant and better able to scale for users with many Droplets. For all the information, find the full API reference documentation here.

    The API also continues to offer the ability to list “neighbors” for a specific Droplet by sending a GET request to /v2/droplets/$DROPLET_ID/neighbors. This endpoint will continue to function without change.

    We apologize for the inconvenience. If you need guidance on this transition, reach out to the team by opening a support ticket.

December 1

  • Tax collection for Belarus has begun. Charges will appear on the January invoice.

November 2019

November 21

November 20

  • DigitalOcean’s API now supports managing a database cluster’s firewall rules (known as “trusted sources” in the control panel) as well as the ability to configure the SQL mode used by MySQL clusters.

    Using the /v2/databases/$DATABASE_ID/firewall endpoint, you can specify which resources should be able to open connections to your database. You may limit connections to specific Droplets, Kubernetes clusters, or external IP addresses. When a tag is provided, any Droplet or Kubernetes node with that tag applied to it will have access. For example, the body a PUT request might look like:

    {
      "rules": [
        {"type": "ip_addr", "value": "192.168.1.1"},
        {"type": "droplet", "value": "163973392"},
        {"type": "k8s", "value": "ff2a6c52-5a44-4b63-b99c-0e98e7a63d61"},
        {"type": "tag", "value": "backend"}
      ]
    }
    

    To configure the SQL modes for a MySQL cluster, use the /v2/databases/$DATABASE_ID/sql_mode endpoint. For example, the body a PUT request might look like:

    {
      "sql_mode": "ANSI,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION,NO_ZERO_DATE,NO_ZERO_IN_DATE"
    }
    

    For more information, see the full API reference documentation for managed databases.

November 19

November 14

November 13

  • Released v1.11.0 of the DigitalOcean Terraform Provider. Learn more in the Terraform Changelog.

November 8

November 4

November 1

October 2019

October 31

  • Memory-Optimized Droplets are now in general availability and are available in the NYC1 and SFO2 datacenter regions.

  • Released v1.10.0 of the DigitalOcean Terraform Provider. Learn more in the Terraform Changelog.

October 23

October 21

  • Ubuntu 19.10 base image is now available in the control panel and via the API.

October 11

  • Users can now see the sign-in method (email, email + 2FA, Google, or GitHub) for team members on the team account page in the control panel.

October 3

September 2019

September 30

  • Released v1.8.0 of the DigitalOcean Terraform Provider. Learn more in the Terraform Changelog.

September 24

September 23

  • DigitalOcean now supports 3-D Secure (3DS) second-factor payment authentication, allowing us to accept payment from banks that require it.

September 20

  • The Billing page in the control panel now splits the costs displayed between payment due and the amount not yet billed for the active billing cycle.

September 10

September 6

September 4

September 1

  • Value Added Tax (VAT) collection for South Korea and Quebec Sales Tax (QST) collection for Quebec, Canada have begun. Charges will appear on the October invoice.

August 2019

August 27

August 26

  • Volume limits for verified accounts have been raised from 10 volumes per account/500 GB of volume data per region to 100 volumes per account/16 TB per region. Unverified accounts are still limited to 10 volumes/500 GB. Learn more about account verification.

August 23

August 22

  • The /v2/volumes?name=$VOLUME_NAME endpoint now lists all volumes that match the specified name as a query parameter. For more information, see the API v2 reference documentation on list Block Storage volumes filtered by name.

August 20

  • Managed Databases for MySQL and Redis have been released in early availability in the NYC1, FRA1, and SFO2 datacenter regions. Learn more in the MySQL and Redis announcement blog post.

  • DigitalOcean Load Balancers no longer support downgrading TLS connections to TLS 1.0. We will stop supporting TLS 1.1 later this year.

  • Today DigitalOcean’s Managed Database service launched support for two new database engines, MySQL and Redis. Both are currently in Limited Availability and can initially be used in the NYC1, FRA1, and SFO2 regions.

    When creating a new database cluster using the API, you must specify the engine attribute to select which type of database to use (mysql for MySQL or redis for Redis). For example, to create a new Redis cluster, make a POST to the /v2/databases endpoint with a JSON body like:

    {
      "name": "cache-01",
      "engine": "redis",
      "version": "5",
      "region": "nyc1",
      "size": "db-s-1vcpu-2gb",
      "num_nodes": 2
    }
    

    See the full API reference documentation for all the details. For more information about DigitalOcean Managed Databases including the roll-out plan for additional regions, check out the blog post announcing the release.

August 19

  • You can now create a maximum of one snapshot of a volume every 10 minutes. See the snapshots overview for more details.

  • Began the incremental release of new block storage volume limits. By the end of the release, all verified accounts will be able to create up to 100 volumes or use a total of 16 TB of volume data per region. Unverified accounts will be allowed 10 volumes or to use a total of 500 GB per region.

  • Floating IP Address rate limit information was added to the DigitalOcean API Documentation.

August 14

  • The default Ubuntu x64 base image has been updated from 18.04.1 to 18.04.3. For details about 18.04.3, see the Ubuntu release notes.

August 13

  • The credit card input form on the billing page in the control panel has been modified to simplify billing address entry.

August 5

  • Released version 1.6.0 of the DigitalOcean Terraform provider.

July 2019

July 29

  • Released doctl version 1.24.1, which is also now available in Docker Hub. You can download it with docker pull digitalocean/doctl.

July 19

July 18

July 12

  • FreeBSD 12 (ufs & zfs) images have been updated to fix a bug related to private networking and SSH keys.

  • FreeBSD 11.3 base image is now available in the control panel and via the API.

July 11

  • DigitalOcean users can now sign up and sign in to DigitalOcean with GitHub OAuth. Users can switch their login type between password-based, Google OAuth, and GitHub OAuth.

July 9

  • Downloadable CSV invoices available on the control panel billing page have been updated to include project names for each Droplet.

July 8

July 3

  • Kubernetes Monitoring Stack (Beta), FASTPANEL, SolidInvoice, and OpenCart third-party One-Click applications were released.

  • The installation repo for the metrics agent has been moved to DigitalOcean Spaces.

July 2

  • The Prometheus 2.9.2, RethinkDB 2.4.0, Mattermost 5.12.0, and Buddy third-party One-Click applications were released.

June 2019

June 25

  • The ttl of a domain record now has a minimum value of 30 seconds, and if not set, the default value has changed from 1800 to the ttl of the SOA record.

June 17

  • 6-hour and 1-day alert policies for Droplets and Kubernetes worker nodes have been deprecated. No new alert policies with these intervals can be created. Existing alert policies using these intervals will remain in place until 1 August 2019, at which point they will be modified to reflect a 1-hour interval.

June 3

  • RancherOS v1.5.2 base images have replaced RancherOS v1.5.1 base images in the control panel and API.

May 2019

May 30

  • DigitalOcean Managed Databases now provide support for private networking. All new database clusters will be provisioned with private networking enabled. Existing clusters will require an update to connect over the private network. This can be triggered in the control panel.

    Databases, read-only replicas, and connection pools will now contain a new private_connection object holding the information needed to access the resource via the private network. Its attributes are identical to the existing connection object, but the values for private_connection.uri and private_connection.host will contain FQDNs only accessible from resources (e.g. Droplets or Kubernetes clusters) within your account and in the same region.

    For more information, see the full Managed Databases API documentation.

May 29

May 22

  • FreeBSD 12.0 (ufs & zfs) base images are now available in the control panel and via the API.

  • FreeBSD 10.4 (ufs & zfs) reached end of life and was removed from the control panel.

  • Fedora 27 reached end of life and was removed from the control panel.

May 21

  • DigitalOcean Kubernetes is now Generally Available. Highlights include:

    • Availability in SGP1 and TOR1.

    • Support for patch version upgrades.

    • Configurable maintenance window and automatic upgrade options.

    • Delete node feature, which removes a specific node from a worker pool.

    • Basic and advanced monitoring insights for resource utilization and deployment status metrics.

  • SOA records are now returned in record results, and you can update the TTL on a SOA record as you would with other records. This allows you to control the negative caching of your domain. SOA records cannot be manually deleted or created on a domain, they are created when the domain is created, and cleaned up on the domain deletion.

  • Today, we are promoting the Kubernetes API to General Availability. As part of this release, we have also extended the API with additional functionality:

    • When creating or updating a cluster, you may now configure a maintenance window policy specifying the day of the week and time of day that updates should take place for the cluster. Additionally, setting a cluster’s auto_upgrade attribute to true will specify that the cluster can be automatically upgraded to new Kubernetes patch releases (e.g. 1.13.1 to 1.13.2) during its maintenance window.

    • An upgrade endpoint is now available to imminently trigger an upgrade to a newer patch release of Kubernetes at your own convienience. You may list available upgrades for your cluster using the upgrades endpoint.

    • In order to give users finer control over individual nodes, the recycle endpoint has been deprecated. Instead, we now offer the ability to delete or replace specific nodes in a node pool. By default, workloads will be drained from the node before deletion. Appending the skip_drain=1 query parameter to the request will cause the node to be imminently deleted. Appending the replace=1 query parameter to the request will cause the node to be replaced by a new one after it has been deleted.

    For the full details, see the API reference documentation for Kubernetes.

    Thank you to everyone who took the time to provide us with feedback.

May 16

  • Our referral program offer has changed from $100 for 60 days to $50 for 30 days. This change applies only to new referrals. Existing users with referral credits will retain their current balance and credit expiration dates.

May 9

  • Spaces are now available in the Frankfurt (FRA1) region.

  • 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.

  • Released v1.3.0 of the DigitalOcean Terraform Provider. Learn more on the Terraform Changelog.

May 7

  • Creating Spaces in NYC3 is now re-enabled.

May 3

May 1

April 2019

April 30

  • Ubuntu 14.04 reached end of life and was removed from the control panel.

April 24

  • DOKS node pools can now be named at creation time.

  • DOKS master nodes now automatically rotate logs to avoid disk space issues.

April 23

April 18

April 16

  • The /v2/volumes/$volume_id/snapshots endpoint now accepts tags at creation time, and these are reflected on the /v2/snapshots endpoint. Volume snapshot tags may now be managed with the /v2/tags endpoint as well. For more information, see the API reference documentation for both block storage volumes and tags.

April 10

April 9

  • The new metrics agent is fully released into production. Highlights include:

    This will be the default agent used by our managed databases and Kubernetes products. All agent installations on or after this date will receive the new agent by default. On 8 July 2019, the legacy metrics agent will be deprecated, meaning users will no longer be able to view metrics from Droplets running the legacy agent. You can upgrade to the new agent at any time.

  • Spaces, DigitalOcean’s object storage solution, includes a built-in CDN. Today we’ve added the ability to use custom subdomains with your CDN endpoints. When configuring your CDN via the API, you can now set the custom_domain attribute to use a subdomain with the endpoint. When a custom subdomain is in use, the certificate_id attribute is also required. Its value must be the the ID of a DigitalOcean managed SSL certificate. For example, the body of your request to enable a CDN might look like:

    {
      "origin": "static-images.nyc3.digitaloceanspaces.com",
      "certificate_id": "892071a0-bb95-49bc-8021-3afd67a210bf",
      "custom_domain": "static.example.com"
    }
    

    See here for more information about using the API to configure Spaces CDN endpoints.

April 5

April 2

April 1

  • The Zabbix and Mastodon third-party One-Click applications were released.

  • To help customers track their credits, beginning in April we will send invoice emails when customers use any resources during a billing period, regardless of an account’s outstanding balance. Previously, invoices were sent only when the outstanding balance exceeded the threshold for automatic payments.

March 2019

March 30

March 27

March 20

  • DOKS customers will now be able to see the cost of their Kubernetes nodes and load balancers aggregated by cluster name within a Kubernetes clusters group on their invoice. Block storage volumes or block storage volume snapshots used in a DOKS cluster are not yet included in the cluster aggregation.

March 19

  • DigitalOcean Load Balancers now support PROXY protocol version 1.

  • DigitalOcean Load Balancers now support using PROXY Protocol to pass information like origin IP addresses and port numbers from connecting client requests along to the backend service. This can be configured using the API by setting the new enable_proxy_protocol attribute to true when creating a new Load Balancer or updating an existing one.

    See here for more information about using PROXY Protocol with DigitalOcean Load Balancers.

March 14

March 5

March 4

March 1

  • The following third-party One-Click applications were released: CloudBees, Jenkins, cPanel, Passbolt, Directus, and Nimbella.

February 2019

February 28

February 27

February 26

February 15

  • As announced on September 5, 2018, the last_tagged attribute returned in response to GET requests to the /v2/tags or /v2/tags/$TAG_NAME endpoints has been deprecated. Beginning March 1st, 2019, last_tagged will no longer be populated in favor of the last_tagged_uri attribute.

    For example, a GET request to /v2/tags/frontend currently might return:

    {
      "tag": {
        "name": "frontend",
        "resources": {
          "count": 3,
          "last_tagged_uri": "https://api.digitalocean.com/v2/droplets/132000916",
          "droplets": {
            "count": 3,
            "last_tagged": {
              "id": 132000916,
              "name": "suspicious-bhabha-u8zq",
              "memory": 2048,
              "vcpus": 2,
              "disk": 60,
              "locked": false,
              "status": "active",
              "kernel": null,
              "created_at": "2019-02-13T05:29:52Z",
              "features": [
                "private_networking"
              ],
              "backup_ids": [],
              "next_backup_window": null,
              "snapshot_ids": [],
              "image": {
                "id": 43509743,
                "name": "do-kube-1.12.3",
                "distribution": "Debian",
                "slug": null,
                "public": false,
                "regions": [
                  "ams2",
                  "ams3",
                  "blr1",
                  "fra1",
                  "lon1",
                  "nyc1",
                  "nyc2",
                  "nyc3",
                  "sfo1",
                  "sfo2",
                  "sgp1",
                  "tor1"
                ],
                "created_at": "2019-02-11T20:38:04Z",
                "min_disk_size": 20,
                "type": "snapshot",
                "size_gigabytes": 2.99
              },
              "volume_ids": [],
              "size": {
                "slug": "s-2vcpu-2gb",
                "memory": 2048,
                "vcpus": 2,
                "disk": 60,
                "transfer": 3,
                "price_monthly": 15,
                "price_hourly": 0.02232,
                "regions": [
                  "ams2",
                  "ams3",
                  "blr1",
                  "fra1",
                  "lon1",
                  "nyc1",
                  "nyc2",
                  "nyc3",
                  "sfo1",
                  "sfo2",
                  "sgp1",
                  "tor1"
                ],
                "available": true
              },
              "size_slug": "s-2vcpu-2gb",
              "networks": {
                "v4": [
                  {
                    "ip_address": "192.0.2.255",
                    "netmask": "255.255.240.0",
                    "gateway": "192.0.2.1",
                    "type": "public"
                  },
                  {
                    "ip_address": "10.136.121.81",
                    "netmask": "255.255.0.0",
                    "gateway": "10.136.0.1",
                    "type": "private"
                  }
                ],
                "v6": []
              },
              "region": {
                "name": "New York 1",
                "slug": "nyc1",
                "sizes": [
                  "s-1vcpu-3gb",
                  "s-1vcpu-1gb",
                  "s-3vcpu-1gb",
                  "s-1vcpu-2gb",
                  "s-2vcpu-2gb",
                  "s-2vcpu-4gb",
                  "s-4vcpu-8gb",
                  "s-16vcpu-64gb",
                  "s-6vcpu-16gb",
                  "s-8vcpu-32gb",
                  "s-12vcpu-48gb",
                  "s-20vcpu-96gb",
                  "s-24vcpu-128gb",
                  "s-32vcpu-192gb"
                ],
                "features": [
                  "private_networking",
                  "backups",
                  "ipv6",
                  "metadata",
                  "install_agent",
                  "server_id",
                  "management_networking"
                ],
                "available": true
              },
              "tags": [
                "frontend"
              ]
            },
            "last_tagged_uri": "https://api.digitalocean.com/v2/droplets/132000916"
          },
          "images": {
            "count": 1,
            "last_tagged_uri": "https://api.digitalocean.com/v2/images/42991114"
          },
          "volumes": {
            "count": 0
          }
        }
      }
    }
    

    Following this change, the new response would look like:

    {
      "tag": {
        "name": "frontend",
        "resources": {
          "count": 3,
          "last_tagged_uri": "https://api.digitalocean.com/v2/droplets/132000916",
          "droplets": {
            "count": 3,
            "last_tagged_uri": "https://api.digitalocean.com/v2/droplets/132000916"
          },
          "images": {
            "count": 1,
            "last_tagged_uri": "https://api.digitalocean.com/v2/images/42991114"
          },
          "volumes": {
            "count": 0
          }
        }
      }
    }
    

    For additional information, see the full API reference documentation for tags.

February 14

  • DigitalOcean Managed Databases were released with support for PostgreSQL v10 and v11.

  • Today DigitalOcean’s Managed Database service, including its API, has entered Limited Availability. In order to access these new endpoints, you must first enable Managed Databases on your account by opting-in via the cloud control panel. Once enabled, you will be able to create, scale, and manage your database clusters via the API. For example, to create a new database cluster, make a POST to the /v2/databases endpoint with a JSON body like:

    {
      "name": "backend",
      "engine": "pg",
      "version": "10",
      "region": "nyc3",
      "size": "db-s-1vcpu-2gb",
      "num_nodes": 2
    }
    

    The response will include a full JSON representation of the database cluster. The initial value of the cluster’s status attribute will be “creating.” When the cluster is ready for use, this will transition to “online.”

    For the all the details, see the full API reference documentation for DigitalOcean Managed Databases.

February 13

February 6

February 5

  • Tag support for block storage volumes was completed in the public API. The /v2/volumes endpoint displays tags and supports adding them to volumes at creation time. You can manage volume tags with the /v2/tags endpoint as well.

  • The /v2/volumes endpoint now displays tags and supports adding them to volumes at creation time. Volume tags may now be managed with the /v2/tags endpoint as well. For more information, see the API reference documentation for both block storage volumes and tags.

  • Users with credits will automatically receive an email notification when account usage exceeds their promo code credit and any prepay balance.

February 4

January 2019

January 31

January 30

January 29

January 16

  • The deprecated 16.04 One-Click LAMP slug, lamp-16-04, was removed from the API.

January 14

January 7

January 1

December 2018

December 20

December 12

December 11

  • API support for Kubernetes Limited Availability was made publically available to all users who opt-in. This included API documentation and support in official clients (godo, doctl, droplet_kit).

  • The following updates were released for DigitalOcean Kubernetes:

    • Any user can opt into Kubernetes during early availability via the control panel.
    • Users can rename clusters.
    • Users can edit tags associated with clusters and worker pool.
    • A guided walkthrough helps users set up their kubectl and kubeconfig properly and provides example manifests to make it easier to get started.
    • The node pool settings to add, remove, and scale node pools has been moved to the ‘Nodes’ tab for a more streamlined experience.
    • The cluster provisioning status bar more accurately reflects the cluster creation progress.
    • Users can view the estimated monthly cost for their clusters.
    • Users can view a breakdown of total cluster capacity including CPU, Memory, Disk cluster wide.
    • Users can create and manage Kubernetes clusters, worker pools, and configuration using doctl.

  • Today we opened up access to the DigitalOcean Kubernetes service for all users. As part of this release, the API is now also available to all. While still in Limited Availability, you must first enable Kubernetes on your account by opting-in via the cloud control panel to access these endpoints.

    Once enabled, you will be able to list, create, or delete clusters as well as scale node pools up and down, recycle individual nodes, and retrieve the kubeconfig file for use with a cluster via the API. For example, to create a new cluster with a node pool using three s-2vcpu-2gb Droplets, make a POST to the /v2/kubernetes/clusters endpoint with a JSON body like:

    {
      "name": "prod-cluster-01",
      "region": "nyc1",
      "version": "1.12.1-do.2",
      "tags": ["production"],
      "node_pools": [
        {
          "size": "s-2vcpu-2gb",
          "count": 3,
          "name": "woker-pool"
        }
      ]
    }
    

    The response will include a full JSON representation of the cluster. The initial value of the cluster’s status.state attribute will be “provisioning.” When the cluster is ready for use, this will transition to “running.” You can use the /v2/kubernetes/options endpoint to find the available versions of Kubernetes as well as the supported regions and Droplet sizes.

    Once ready, you can retrieve the credentials for use with the cluster by sending a GET request to /v2/kubernetes/clusters/$K8S_CLUSTER_ID/kubeconfig. The response will be a kubeconfig file in yaml format. This file can be used to connect to and administer the cluster using the Kubernetes command line tool, kubectl. For more information, see “How to Connect to a DigitalOcean Kubernetes Cluster with kubectl.”

    For the all the details, see the full API reference documentation for DigitalOcean Kubernetes.

December 7

  • The minimum size for a Kubernetes node was changed to the 2 GB Memory / 1 vCPU plan.

December 1

November 2018

November 26

  • The Projects API was released to general availability.

  • Today, we are promoting the Projects API to General Availability. For the full details, see the API reference documentation for both Projects and Project Resources.

    Thank you to everyone who took the time to provide us with feedback.

November 19

November 13

November 1

  • Value Added Tax (VAT) collection for Switzerland and Turkey has begun. Charges will appear on the December invoice.

October 2018

October 26

October 24

October 23

  • Droplets created from custom images now support snapshots and backups.

October 19

October 18

October 16

  • The initial beta release of our Projects API is now available for testing allowing you to manage projects and assign resources to them with our API and official clients. See the API changelog for additional details.

  • Today, we are launching a beta of our new Projects API. Projects enable you to group your resources in ways that align with the applications you host on DigitalOcean, and now you can do so via our API as well. This initial release includes the ability to:

    • Create, list, retrieve, update, and delete Projects
    • Assign existing resources to a Project
    • List resources in a Project

    Additionally, we’ve added beta support for Projects to our official clients (Droplet Kit, godo, and doctl).

    You can create a new project by sending a POST request to the /v2/projects endpoint including a body like:

    {
      "name": "my-web-api",
      "description": "My website API",
      "purpose": "Service or API",
      "environment": "Production"
    }
    

    To assign resources to a project, send a POST request to /v2/projects/$PROJECT_ID/resources including a list of those resources in the body:

    {
      "resources": [
        "do:droplet:123456",
        "do:floatingip:192.168.99.100",
        "do:space:static-assets",
        "do:volume:0e250b2a-8a01-11e8-96ae-0242ad114410"
       ]
    }
    

    Resources are identified by uniform resource names or URNs, a string consisting of the type of resource and its unique identifier. A valid URN has the following format: do:resource_type:resource_id. For the full details, see the API reference documentation for both Projects and Project Resources.

    Note that as this is a beta release, we may make additional changes based on your feedback. So let us know how you’re using projects, and follow along with the API changelog for updates.

October 5

October 2

  • Released v1.0.1 of the DigitalOcean Terraform Provider. Learn more on the Terraform Changelog.

October 1

September 2018

September 27

  • Released the Spaces content delivery network (CDN).

  • Deprecated the Spaces free trial.

  • Released v1.0.0 of the DigitalOcean Terraform Provider, including new attachment resources for volumes and floating IPs, support for Let’s Encrypt certificates, auto-formatting for volumes, and CAA domain records, and more. Learn more: https://do.co/terraform-changelog

  • Today’s release brings Content Delivery Network (CDN) support to Spaces, DigitalOcean’s object storage solution. This can be configured and managed using our API. By sending requests to /v2/cdn/endpoints, you can list, create, or delete CDN endpoints as well as purge cached content.

    To enable the CDN for your Space, send a POST request to /v2/cdn/endpoints. In the JSON body of your request, specify the origin of your content and the desired TTL. For example:

    {
      "origin": "static-images.nyc3.digitaloceanspaces.com",
      "ttl": 3600
    }
    

    Currently, the origin must be a DigitalOcean Space.

    To purge cached content from a CDN endpoint, send a DELETE request to /v2/cdn/endpoints/$ENDPOINT_ID/cache. The body of the request should include a files attribute containing a list of cached file paths to be purged. A path may be for a single file or may contain a wildcard (*) to recursively purge all files under a directory. When only a wildcard is provided, all cached files will be purged. For example, the body of your request might look like:

    {
      "files": [
        "assets/img/hero.png",
        "assets/css/*"
      ]
    }
    

    For additional details, see the API reference documentation for managing CDN endpoints.

September 25

  • Released custom image support which allows customers to upload their Linux and Unix-like images to their DigitalOcean account and use them to create Droplets.

  • Today DigitalOcean released support for uploading custom images, enabling you to create Droplets based on your own Linux virtual machine images. Our image management API has been extended with support as well. By sending a POST to the /v2/images endpoint, you can create a new custom image. The request must contain a url attribute pointing to where the image can be downloaded. The image itself may be in the raw, qcow2, vhdx, vdi, or vmdk format. It can be compressed using gzip or bzip2 but must be smaller that 100 GB after being decompressed. For example, the body of you request might look like:

    {
      "name": "ubuntu-18.04-minimal",
      "url": "http://cloud-images.ubuntu.com/minimal/releases/bionic/release/ubuntu-18.04-minimal-cloudimg-amd64.img",
      "distribution": "Ubuntu",
      "region": "nyc3",
      "description": "Cloud-optimized image w/ small footprint",
      "tags": [
        "base-image",
        "prod"
      ]
    }
    

    To make organizing your images easier, we’ve also extended tagging support to custom images as well as Droplet snapshots. For additional details, see the API reference documentation for creating custom images and tagging resources.

September 13

  • Removed deprecated Machine Learning/Artificial Intelligence and MEAN One-Clicks from the control panel.

  • New One-Click Application Droplets that you create with the control panel will be based on Ubuntu 18.04 LTS. For the next 60 days (through November 12, 2018 11:59pm EST), Ubuntu 16.04 LTS-based One-Clicks will continue to be available alongside the 18.04 version through the API.

September 11

  • Removed the list of environments (Production, Staging, Development) from the list of project purposes when creating projects. Added them as a separate dropdown on the Project Settings page.

  • Fixed a bug where a project containing only domains displayed an empty state that required users to scroll to access their domains.

  • Fixed a bug where domains with capital letters were not displaying the project on the Domain page.

  • Began incremental release of invoice aggregation for users with more than 3000 invoice line items.

September 10

September 5

  • When listing or getting tags by sending a GET request to /v2/tags or /v2/tags/$TAG_NAME, the response payload currently includes a last_tagged value inside the tag’s resources.droplets containing a full representation of the resource. This payload is considerably nested and adds additional overhead to the request. In order to improve performance as well as lay the groundwork for bring tagging support to additional resources, this attribute is being deprecated. Beginning March 1st, 2019 last_tagged will no longer be populated in favor of the new last_tagged_uri attribute introduced today.

    For all resources (and each resource type supported), the last_tagged_uri attribute contains a string indicating the URI which can be used to retrieve details about that specific resource. If you need information about the last tagged resource specifically, issuing another call to that URI will provide you with all the data for that resource.

    Additionally, a count attribute describing how many resources overall have been tagged with the tag in question has been added. Each individual resource type will continue providing a count attribute.

    If you need guidance on transitioning from using last_tagged to using of the new last_tagged_uri attribute, reach out to the team by opening a support ticket.

August 2018

August 14

August 9

August 1

July 2018

July 27

  • The default Ubuntu x64 base image has been updated from 16.04.4 to 18.04.1. For details about 18.04.1, see the Ubuntu release notes.

July 25

  • Released the following control panel updates:

    • Users can organize their resources into projects to fit the way they work. Projects allow users to group their Droplets, Spaces, Load Balancers, domains, and Floating IPs to align with the applications, environments, clients, and projects that they host on DigitalOcean
    • The main navigation of the control panel moved from top navigation to left navigation with updated styles.

    The changes are scheduled to reach all users by July 28.

July 24

  • You can now edit the card holder name, expiration date, CVC code, and billing address for existing credit card on the Account Billing page.

July 19

July 18

July 17

July 16

July 12

July 11

July 10

  • Private networking isolation was released in the AMS2, BLR1, and TOR1 datacenters. Communication over the private network in those datacenters is now restricted to other resources within an account or team.

July 3

July 1

June 2018

June 25

  • Released new documentation site for the DigitalOcean Control Panel with updated content and product-specific navigation and search to help readers more readily learn how to use DigitalOcean.

June 22

  • GitLab One-Click application has been updated with the following changes:

    Updated From To
    Kernel 4.4.0-119-generic 4.4.0-128-generic
    GitLab Community Edition 10.6.4 dee2c87 11.0.0 b84bfb5

  • Spaces will send billing data for active users within 2 hours of usage, down from a 4-5 day processing time. Previously, some users who were not billed for overages because of the processing delay may see their bill go up based on their actual usage.

  • New Domain resources can now be created via the DigitalOcean v2 API without providing an IP address. The previous behavior, which would automatically create an A record pointing to the apex domain, will be retained for backwards-compatibility when an IP address is provided.

    This example demonstrates how to create a new domain without providing an IP address:

    curl -X POST -H "Content-Type: application/json" \
        -H "Authorization: Bearer $DIGITALOCEAN_API_TOKEN" \
        -d '{"name":"example.com"}' \
        "https://api.digitalocean.com/v2/domains"
    

    For more information, see the full Domains API documentation.

June 19

June 13

  • Updated RancherOS container image from 12.0 to 14.0. Customers can learn more about the new version on Rancher’s release page.

June 11

  • Expanded Droplet View allows customers using the Dashboard to click on a Droplet and quickly view additional information about the Droplet without having to go to the Droplet Page. It also updates the list of Droplets to display at a glance whether Backups are on/off and if a Floating IP is attached.

June 5

May 2018

May 22

  • Block Storage Volumes for Ubuntu, Fedora, Debian 8+, CentOS, and Fedora Atomic can be automatically formatted and mounted when they are created.

  • The /v2/volumes endpoint has been updated to support automatically formatting the filesystem of newly created Block Storage volumes. Volume resources now expose two new attributes: filesystem_type and filesystem_label. They can be used to specify the filesystem and the label to be applied. Currently, the available filesytem types are ext4 and xfs.

    For example, here is a request creating a new volume formatted with an EXT4 filesystem:

      curl -X POST \
      -d '{"name":"volume-nyc3-01","region":"nyc3","filesystem_type":"ext4","filesystem_label":"example","size_gigabytes": 100}' \
      -H "Content-Type: application/json" \
      -H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
      https://api.digitalocean.com/v2/volumes
    

    Additionally, Ubuntu, Debian, Fedora, Fedora Atomic, and CentOS Droplets created on or after April 26, 2018 will now automatically mount volumes with pre-formatted filesystems when attached. Attaching pre-formatted volumes to other Droplets is not recommended. When the filesystem_type attribute is not provided, volumes will continue to be presented as raw block devices and require additional configuration.

    When retrieving an existing Block Storage volume, filesystem_type and filesystem_label will reflect the current filesystem and label used on the volume even if these were applied manually.

    For more information, see the full API documentation for Block Storage Volumes.

May 17

  • Turned on Droplet Search in the top navigation for all users. Allows users to quickly search for Droplets by name or IP address and go directly to the Droplet Page.

May 16

May 11

  • Fixed issue with 2FA QR code generation for authenticator applications. Users with usernames over 26 characters were unable to generate a QR code. We now render up to 65 characters of a user’s entire email address and truncate if it is longer. This prevents errors for users with long email addresses, and renders more information in authenticator applications to help users with multiple accounts have more context.

May 8

  • Load Balancers v1.5 is released to general availability in all regions, including backend upgrades, Let’s Encrypt Integration, and HTTP/2 Support.

  • Today, DigitalOcean released a number of Load Balancer improvements including support for using SSL/TLS certificates automatically generated by Let’s Encrypt. Our Certificate management API has been updated to support automatically generating Let’s Encrypt certificates in addition to uploading custom, user-generated certificates.

    A request to generate a new SSL/TLS certificate using Let’s Encrypt would look like:

        curl -X POST \
        -H "Content-Type: application/json" \
        -H "Authorization: Bearer $DO_TOKEN" \
        -d '{"name": "le-cert-01", "type": "lets_encrypt", "dns_names": ["www.example.com","example.com"]}' \
        "https://api.digitalocean.com/v2/certificates"```
    

    The new type attribute must be set to lets_encrypt when using Let’s Encrypt. If omitted, it will default to custom in order to maintain backwards compatibility. For additional details, see the Certificate management API reference documentation.

    For more information on how to use Let’s Encrypt with DigitalOcean Load Balancers, see this tutorial on our community site.

May 1

  • Fedora 28 base image has been released using the slug fedora-28-x64 and fedora-28-x64-atomic. The images are now public to all users.

April 2018

April 30

  • Burst support rolled out to all nine block storage regions.

    Performance Expectations

    Droplet Type IOPS Throughput
    Standard 5K 200 MB/s
    Std (Burst) 7.5K 300 MB/s
    Optimized 7.5K 300 MB/s
    Optimized (Burst) 10K 350 MB/s

April 27

April 24

April 20

  • Debit cards from any country can be used for payment once a temporary pre-authorization charge of $1 is successful.

April 17

  • 1vCPU-Optimized Droplet launched.

  • Spaces users no longer need to cancel their Spaces subscription via the Spaces UI when they want to stop using Spaces. Now, any time a Spaces user destroys their last Space, their pro-rated $5/month billing (if not in the free trial period) stops. Overage charges still apply if they were incurred before deletion of the last Space.

March 2018

March 30

March 20

  • Launched the new Dashboard experience to the control panel. The Dashboard replaces the Droplets page as the new default home page of the control panel. It provides at-a-glance visibility into active resources, like Droplets, Spaces, load balancers, floating IPs, and domains, month-to-date current billing usage, shortcuts to team management, and other common tasks without having to navigate to different and often hard-to-find sections of the control panel.

March 14

February 2018

February 15

  • Resolved an issue where some Spaces customers were being rate limited even though they were well below the rate limiting threshold.

February 12

  • Added improvements to reduce timeouts on the Spaces API.

  • Number of days left in your 60-day Spaces free trial is now shown on trial opt-in page and on details modal.

February 9

February 6

  • Block storage cluster in Bangalore and London upgraded to Ceph Luminous, reducing median cluster latency by 50%

February 2

January 2018

January 29

  • Spaces now support:

    • Version 4 of pre-signed URLs, allowing for easier use of 3rd party S3 compatible libraries.
    • Scheduled deletion of objects via bucket lifecycle methods in the Spaces API.
    • Previews of image, audio, and video files that are moused over in the control panel file browser.

January 25

  • Spaces are now available in the Singapore (SGP1) region.

January 17

  • Static site hosting and custom domains for Spaces have been released in private beta. Email [email protected] to participate.

January 16

  • DigitalOcean upgrades Memory, SSD and vCPU across all Standard, Flexible and Optimized Droplet plans.

  • Today, we announced wide-ranging changes to our Droplet plans, bringing improved resources across the board. These new plans are now available via the API and can be referenced using their respective size slugs.

    Size slugs are human-readable strings used to specify the type of Droplet in certain API requests. In the past, size slugs were typically based on the amount of RAM provided with the plan (e.g. 1gb). Moving forward, we are standardizing on a format comprised of the identifier for the Droplet’s class, the vCPU count, and the amount of RAM in order to provide more flexibility in the plans we are able to offer you. For example, our new $5 per month Standard Droplet comes with 1 vCPU and 1 GB of RAM. So its size slug is. s-1vcpu-1gb.

    Applications and scripts with hard-coded size slugs must be updated to take advantage of these new plans. In order to provide a transition period, 1st Generation Droplet plans will continue to be available via the API using the legacy size slugs. We will provide additional notice before their removal.

    The table below shows the new 2nd Generation Standard Droplet plans along with their corresponding size slug. For always up-to-date information on available plans and pricing, see our pricing page.

    Class Slug vCPUs RAM Disk Transfer Monthly Price
    Standard s-1vcpu-1gb 1 1 GB 25 GB 1 TB $5
    Standard s-1vcpu-2gb 1 2 GB 50 GB 2 TB $10
    Standard s-1vcpu-3gb 1 3 GB 60 GB 3 TB $15
    Standard s-2vcpu-2gb 2 2 GB 60 GB 3 TB $15
    Standard s-3vcpu-1gb 3 1 GB 60 GB 3 TB $15
    Standard s-2vcpu-4gb 2 4 GB 80 GB 4 TB $20
    Standard s-4vcpu-8gb 4 8 GB 160 GB 5 TB $40
    Standard s-6vcpu-16gb 6 16 GB 320 GB 6 TB $80
    Standard s-8vcpu-32gb 8 32 GB 640 GB 7 TB $160
    Standard s-12vcpu-48gb 12 48 GB 960 GB 8 TB $240
    Standard s-16vcpu-64gb 16 64 GB 1,280 GB 9 TB $320
    Standard s-20vcpu-96gb 20 96 GB 1,920 GB 10 TB $480
    Standard s-24vcpu-128gb 24 128 GB 2,560 GB 11 TB $640
    Standard s-32vcpu-192gb 32 192 GB 3,840 GB 12 TB $960

    Available Droplet plans, the resources they provide, and the size slug used to identify them can be accessed programmatically by querying the /v2/sizes endpoint.

January 9

September 2017

September 13

  • Domain Record resources have been updated to add support for CAA records. As specified in RFC-6844, this record type can be used to specify which certificate authorities (CAs) are permitted to issue certificates for a domain.

    For example, in order to restrict TLS/SSL certificate creation for example.com to letsencrypt.org, you would use a request like:

      curl -X POST \
      -d '{"type":"CAA","name":"@","data":"letsencrypt.org.","priority":null,"port":null,"ttl":1800,"flags":0,"tag":"issue"}' \
      -H "Content-Type: application/json" \
      -H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
      https://api.digitalocean.com/v2/domains/example.com/records
    

    For more information on how to use CAA records, see this tutorial on our community site.

April 2017

April 14

  • Our API has been extended to support configuring the TTL value for individual domain records. This can be done when creating a new record as well as when updating an existing one via a PUT request. See the domain record documentation for further information.

March 2017

March 28

  • Our API currently offers the ability to “rename” a tag by sending a PUT request to /v2/tags/$TAG_NAME. Due to low usage and operational complexities involved with its maintenance, we are deprecating this functionality. Beginning April 26th, 2017 all requests to this endpoint will respond with an HTTP status of 410 (Gone). A tag’s name also serves as its unique identifier. We’ve found that the ability to change a tag’s name introduces unneeded complexity. If you need guidance on this transition, reach out to the team by opening a support ticket.

November 2016

November 10

  • You may now pass tags as an attribute when creating one or more new Droplets. This optional parameter will create and apply the specified tag(s) to the newly created Droplet(s). For more information see create Droplet documentation.

October 2016

October 5

April 2016

April 13

  • Size objects now contain a size\_gigabytes attribute which represents the physical size of the image in gigabytes. For more information see the images documentation.

March 2016

March 22

December 2015

December 14

November 2015

November 24

  • Account objects now contain a floating\_ip\_limit attribute which provides the maximum number of floating IPs that may be provisioned by the account. For more information, see the account documentation.

November 5

July 2015

July 20

  • Account objects now contain status and status_message attributes, describing whether an account is locked, active or has a pending warning. For more information, see the account documentation.

July 14

  • We’ve deprecated final (temporary) snapshots and therefore temporary is no longer an acceptable value for type for a snapshot.

May 2015

May 20

May 1

  • Since releasing version 2 of our API nearly a year ago and officially bringing it out of beta last month, we’ve seen a tremendous uptake of usage by our community. As the ecosystem of tools and libraries continues to grow, we’ve decided that it is time to sunset version 1 of the API.

    Don’t worry! We’re not going to pull the rug out from under you. In order to give everyone time to port their tools, version 1 will not be turned off until Monday, November 9, 2015.

    With its (more) RESTful interface and features like OAuth support, v2 is both powerful and easy to use. Our developer documentation should give you all the information you need to begin the transition. If you have questions, you can always ask on our Community site or on Twitter.

April 2015

April 2

March 2015

March 25

  • The Image action endpoint now responds to a convert attribute, that allows backups and temporary snapshots to be saved permanently as snapshots. For more information, see the image actions documentation.

March 11

  • Images objects now return a type attribute, describing whether they are snapshots, backups or temporary images. For more information, see the images documentation.

March 4

  • Size objects now expose an available boolean attribute, which represents whether new Droplets can be created with the size.

February 2015

February 20

  • All action objects, i.e. those returned by the /v2/actions, /v2/droplets/$ID/actions and /v2/images/$ID/actions endpoint now return a region_slug attribute, in addition to a region attribute. At 00:01 March 20, 2015 UTC, API v2 will start returning an embedded region object at the region attribute, not a slug.

    For example, the API request:

    curl -X GET -H 'Content-Type: application/json' \
        -H 'Authorization: Bearer $DIGITALOCEAN_TOKEN' \
        "https://api.digitalocean.com/v2/actions?page=1&per_page=1"
    

    would return:

    {
      "actions": [
        {
          "id": 36804636,
          "status": "completed",
          "type": "create",
          "started_at": "2014-11-14T16:29:21Z",
          "completed_at": "2014-11-14T16:30:06Z",
          "resource_id": 3164444,
          "resource_type": "droplet",
          "region": {
            "name": "New York 3",
            "slug": "nyc3",
            "sizes": [
              "32gb",
              "16gb",
              "2gb",
              "1gb",
              "4gb",
              "8gb",
              "512mb",
              "64gb",
              "48gb"
            ],
            "features": [
              "virtio",
              "private_networking",
              "backups",
              "ipv6",
              "metadata"
            ],
            "available": true
          },
          "region_slug": "nyc3"
        }
      ],
      "links": {
        "pages": {
          "last": "https://api.digitalocean.com/v2/actions?page=159&per_page=1",
          "next": "https://api.digitalocean.com/v2/actions?page=2&per_page=1"
        }
      },
      "meta": {
        "total": 159
      }
    }
    

February 10

February 8

  • The maximum allowed rate limit per O-Auth token has been increased to 5,000 requests/hour.

January 2015

January 22

  • The images now supports a private filter which will allow you to retrieve all images that are specific to your account (IE: backups and snapshots).

    For more information, you can view the documentation for this endpoint here.

January 20

  • API V2 now validates SSH key IDs and identifiers passed into the Droplet create call. In addition, API V2 now validates that requested features are available for a Droplet (backups, private networking, IPv6 and user data).

November 2014

November 6

  • The API v2 now supports retrieving images by type, to retrieve an image by type, simply append:

    GET /v2/images?type={distribution,application}
    

    Change type to what you would like to retrieve and voilà!

    DropletKit (The Ruby API Client) also supports this functionality as well in Version 1.1.0

    You can view the documentation for this feature here.

October 2014

October 27

  • The JSON object for a droplet no longer contains a nested Size object, but rather a slug called size_slug that references a Size object. See the droplet docs for the updated structure.

    The Image JSON object now includes a min_disk_size attribute that contains the slug of the minimum size droplet required for that image. For example a snapshot of a 1 Gig droplet will have “1gb” as it’s min_disk_size.

August 2014

August 20

  • Remove embedded action_ids from Droplet and Image.

July 2014

July 25

  • Both price\_monthly and price\_hourly were previously strings. This made them harder to work with so we have gone ahead and turned them into floats.

July 2

  • We have tweaked the per_page limits to default to 20 and be a maximum of 200. We have found in our testing, so far, for this to be a good balance of requests versus results. Head on over and read up on pagination.

June 2014

June 25

  • API V2 now supports disabling backups on a Droplet.

  • API V2 now supports expanding a droplet’s disk size, along with other resources.

  • Want to know which regions support IPv6 or Private Networking? It is now possible to check which features are enabled in each region.

June 24

  • It seems adding X- to custom HTTP headers is going out of style.

    So we gone ahead and changed our RateLimit headers to no longer include the X.

    They now look like this:

    RateLimit-Limit:
    RateLimit-Remaining:
    RateLimit-Reset: