Estoy tratando de determinar una estrategia de bajo riesgo para migrar de AWS S3 a DO Spaces para copias de seguridad y subidas. Inicialmente, estoy pensando en hacerlo de la “larga”, es decir:
Migrar las subidas a local
Eliminar la configuración antigua de S3
Agregar la nueva configuración de DO Spaces
Migrar a Spaces
Una ruta alternativa sería crear un contenedor alternativo y configurarlo para usar DO Spaces, pero creo que importar una copia de seguridad en él simplemente sobrescribirá la configuración y lo volverá a conectar a S3.
Sin embargo, me gustaría saber si existe una forma más rápida de hacer lo mismo utilizando alguna herramienta como S3CMD para mover activos de S3 a DO y simplemente cambiar la configuración para vincularlo a DO.
¿Alguna idea al respecto? ¿Cuáles podrían ser los riesgos potenciales?
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.