Estou tentando definir uma estratégia de baixo risco para migrar do AWS S3 para o DO Spaces para backups e uploads. Inicialmente, estou pensando em fazer da maneira “longa”, ou seja:
Migrar os uploads para local
Remover a configuração antiga do S3
Adicionar a nova configuração do DO Spaces
Migrar para o DO Spaces
Uma alternativa seria levantar um container alternativo e configurá-lo para usar o DO Spaces, mas acho que importar um backup nele simplesmente sobrescreveria as configurações e o conectaria novamente ao S3.
Mas tenho curiosidade em saber se existe um caminho mais curto para fazer o mesmo usando alguma ferramenta como o S3CMD para mover os ativos do S3 para o DO e, em seguida, apenas alterar as configurações para vincular ao DO?
Alguma ideia sobre isso? Quais podem ser os possíveis riscos?
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.