Spaces and copyObject issues/timeouts

Posted February 14, 2021 347 views
DigitalOcean Spaces

Currently trying to the copyObject call from the S3 SDK and it is timing out. We have been noticing this issue occasionally over the last few weeks. Are there currently any known issues with spaces when trying to copy objects from one place to another within the same Spaces domain?


These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
2 answers

Hello, @austinbischoff

There was an Issue with Spaces Availability in FRA1 a few days ago - which was successfully resolved by our engineers.

At the moment everything should be working fine including in NYC3 as well. If you’re still experiencing issues please submit a support ticket with detailed information about the issue and our support team will be more than happy to assist you.


After extensive testing it appears to be a design flaw in the DigitalOcean Spaces implementation itself and I’m quite surprised (and concerned) that DO engineering hasn’t responded to this. Both copy and rename take an unusual amount of time. You can even see this renaming an object in the DO dashboard/ui. A rename shouldn’t take 15-20 seconds. I’m not sure how Amazon handles this in their S3 implementation but it’s almost instant.

I would highly advise anyone considering switching from AWS to DO Spaces to be 100% sure you’ve tested the endpoints you need and to make no assumptions. The API is the same but the infrastructure and underlying design is most certainly not.