Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
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.
It’s been a while, but I just ran into the same problem and the following solution worked: https://meta.discourse.org/t/uploads-migrate-to-s3-fails-with-seahorse-certificate-verify-failed-on-digital-ocean-spaces/141158
In short, the user interface of Digitalocean provides the spaces endpoint with the bucket name as subdomain like “https://<bucketname>.ams3.digitaloceanspaces.com” while the aws-sdk-s3 gem expects only the server path “https://ams3.digitaloceanspaces.com”