We have reenabled the creation of new resources in SFO2 for all customers.
Spaces is now available in BLR1. You can view the availability of all of our products by datacenter in the regional availability matrix.
Spaces now automatically delete any incomplete multipart uploads older than 90 days to prevent billing and to free up storage.
Newer Spaces buckets now have an improved limit of 800 total operations per second. To check whether a bucket has this new limit, see our Spaces rate limits.
All Spaces rate limits have increased to double their previous amount. For a list of the current rate limits, see our Limits page.
Spaces and the Spaces CDN now support HTTP/2 clients. HTTP/2-conformant clients now receive HTTP/2 responses, while others receive HTTP/1.1 responses. In certain cases, such as when an HTTP/2 request has a formatting error, it may downgrade to HTTP/1.1 for operational reasons, as permitted by the HTTP/2 specification.
In order to improve security, DigitalOcean no longer accepts TLS 1.0 and TLS 1.1 connections. This includes connections to www.digitalocean.com, cloud.digitalocean.com, and api.digitalocean.com.
You can now cancel a Space’s scheduled deletion in the control panel. For more details, see How to Destroy Spaces.
Spaces no longer supports downgrading TLS connections to TLS 1.1 or using cipher suites with SHA1 or DHE. Spaces currently returns soft S3 error messages and will gradually transition to hard TLS errors over a 4-6 week period.
Spaces no longer supports downgrading TLS connections to TLS 1.0, and will transition from returning soft S3 error messages to hard TLS errors over the next month.
Managed Let’s Encrypt certificates will begin using Elliptic Curve Digital Signature Algorithm (ECDSA) instead of RSA. ECDSA is equally secure and more computationally efficient than RSA. ECDSA certificates follow the shorter root chain and aren’t rooted using the DST Root CA X3 cross-sign which expired on 30 September 2021.
As we roll out this change, new Let’s Encrypt certificates provisioned for DigitalOcean Load Balancers and Spaces will increasingly use ECDSA and existing certificiates secured with RSA will be secured with ECDSA upon auto-renewal. This change doesn’t require any action from DigitalOcean customers.
We have deprecated TLS DHE ciphers for all load balancers.
The load balancer and Spaces services now support wildcard Let’s Encrypt certificates.
With the completion of the SGP1 capacity augmentation, we have re-enabled the creation of new Spaces in SGP1.
Spaces are now available in SFO3.
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.
We have updated capacity in FRA1 and have resumed the creation of Spaces in that region.
We have temporarily disabled the creation of new Spaces in SGP1 while we update capacity in this region.
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.
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.
v1.17.0 of the DigitalOcean Terraform Provider is now available. This release includes bug fixes and new Spaces data sources.
v1.16.0 of the DigitalOcean Terraform Provider is now available. This release includes VPC support and expanded Spaces support.
The Spaces CDN now has separate caches for unique URLs, including query strings.
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.
We’ve disabled creating new Spaces in AMS3 until we complete maintenance on the datacenter as part of addressing Spaces performance concerns. Learn more about Spaces AMS3 availability.
The installation repo for the metrics agent has been moved to DigitalOcean Spaces.
Spaces are now available in the Frankfurt (FRA1) region.
Creating Spaces in NYC3 is now re-enabled.
Released the Spaces content delivery network (CDN).
Deprecated the Spaces free trial.
Spaces are now available in the SFO2 region.
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.
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.
Resolved an issue where some Spaces customers were being rate limited even though they were well below the rate limiting threshold.
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.
Deletion of a Space via the control panel is disallowed if there are 100,000 or more objects in the Space. Once the Space has less than 100,000 objects within, it can be deleted by the control panel.
Spaces now support:
Spaces are now available in the Singapore (SGP1) region.
Static site hosting and custom domains for Spaces have been released in private beta. Email [email protected] to participate.