AWS S3 からバックアップとアップロード用の DO Spaces への移行について、低リスクな戦略を検討しています。当初は、以下のような「手間のかかる」方法を考えていました。
別のアプローチとして、代替コンテナを起動して DO Spaces を使用するように設定することも考えられますが、バックアップをインポートすると設定が上書きされ、再び S3 に接続されてしまうのではないかと懸念しています。
しかし、S3CMD などのツールを使って S3 から DO へアセットを移動させ、設定を変更して DO にリンクさせるような「ショートカット」的な方法があるかどうか気になっています。
ご意見や、考えられるリスクについて何かご存知でしょうか？
Bhanu, what’s your driver for moving?
Experimentation primarily
Then cost effectiveness.
My AWS free tier comes to an end soon … need to think about these things too!
Mine has expired recently so Iooking for some cost cutting.
I have in past migrated data from S3 to Spaces using S3CMD and I assume it will go through just fine with rclone as well! What I’m more concerned about is rewrites here! Specifically because currently I’m using S3 in addition with CloudFront but I plan to switching to Google Cloud CDN or fastly once my assets have been migrated.
Update: I Moved uploads to local today and the first thing that I’ve come across is that assets (despite being migrated from s3 to local) are taking a long time to be served locally. I don’t want to risk breaking things so presumably I’ll have to wait a few hours until all the uploads are being served from my forum then only I can proceed to setting up DO Spaces!
It doesn’t look like digitalocean is very good at running ceph (the software that they use for spaces). Their ams3 data center’s cluster is pretty broken now. Backups fairly regularly time out. I was very hopeful about this product but am not recommending it at right now.
Agreed, I’d recommend S3 over Spaces for sanity reasons too. I’ve had latency issues with DO Spaces which isn’t the case where I use the S3+CloudFront set up that powers our forum.