Sto cercando di capire una strategia a basso rischio per passare da AWS S3 a DO Spaces per backup e caricamenti. Inizialmente, pensavo di farlo nel modo “lungo”, ovvero:
Spostare i caricamenti in locale
Rimuovere la vecchia configurazione S3
Aggiungere la nuova configurazione DO Spaces
Spostare i dati su Spaces
Un’alternativa potrebbe essere avviare un container alternativo e configurarlo per utilizzare DO Spaces, ma penso che importare un backup al suo interno sovrascriverebbe semplicemente le impostazioni e lo ricollegherebbe nuovamente a S3.
Tuttavia, sono curioso di sapere se esiste una scorciatoia per fare la stessa cosa utilizzando uno strumento come S3CMD per spostare gli asset da S3 a DO e semplicemente modificando le impostazioni per collegarsi a DO.
Avete qualche idea a riguardo? Quali potrebbero essere i potenziali rischi?
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.