We have added the project_id field to the Reserved IP service’s API. The project_id field allows you to create and associate Reserved IPs with a DigitalOcean Project.
Use the project_id and region fields in a Create a new Reserved IP request to create a Reserved IP within a project. You can assign the IP address to a Droplet later using a Reserved IP action request.
We have added the project_id field to the following Reserved IP API responses:
The following pricing changes are now in effect:
A new $4 Droplet with 512MB of memory, 10GB of storage, 1 vCPU, and 500GB of outbound data transfer is now available in NYC1, FRA1, SFO3, SGP1, and AMS3. The slug is s-1vcpu-512mb-10gb.
We have simplified pricing for DigitalOcean Kubernetes and some Managed Databases for better accuracy and predictibility.
The prices of Droplets, Snapshots, Load Balancers, Reserved IPs, and Custom Images have increased.
There is no change to pricing for Spaces, backups, volumes, DigitalOcean Container Registry, or App Platform. There are also no changes to inbound data transfer or bandwidth pricing.
This is our first major price change in 10 years, and we believe the new model better fits our understanding of our customers and the expanded breadth of our offerings. For a more detailed breakdown of the changes, see our blog post on our new pricing.
To improve security, DigitalOcean no longer accepts TLS 1.0 and TLS 1.1 connections. This includes connections to www.digitalocean.com, cloud.digitalocean.com, and api.digitalocean.com.
We have renamed the Floating IP product to Reserved IPs. The Reserved IP service retains the same functionality as the prior service.
We have added new API endpoints and fields (reserved_ips) to reflect the name change, but the service’s original Floating IP endpoints and fields (floating_ips) will remain available until the fall of 2023. Please update any automation, scripts, or services that use these endpoints to reflect these changes.
If you are using the Projects API to query Reserved IP resources, the endpoint still returns reserved IP addresses in the floating_ips field.
You can now assign floating IP addresses to Droplets that use custom images.
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:
private_networking feature is now displayed under the features field under droplet instead of the features field under region.vpc_uuid field now populates with the correct values.type displays base when the Droplet uses a base image (i.e. Ubuntu, CentOS).networks field now includes private and floating IP addresses, if applicable.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.
Floating IP Address rate limit information was added to the DigitalOcean API Documentation.
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.