Piensa en qué pasaría si mañana la máquina no arrancara. Un disco dañado, una actualización que la deja inservible, un borrado por error, alguien que entra donde no debe. Sin una copia de ayer, se pierde todo lo que había dentro, y en AWS no hay a quién llamar: la copia es responsabilidad tuya. AWS tiene con qué hacerla (instantáneas, Data Lifecycle Manager, AWS Backup), pero hay que configurarlo por máquina y por región, y nadie te avisa si un día deja de funcionar.
En Simplio programas las copias de cada máquina y te olvidas: cada día o cada semana, conservando las últimas que le digas y borrando las viejas para no pagar de más. Y, si quieres, cada copia se replica a otra región de AWS, para que un problema en un centro de datos no se lleve también las copias. Si una copia falla, lo sabes por un aviso. Restaurar es un botón.
How it works
You schedule the machine
Every day or every week, at the time you say, and how many copies to keep. If you want, the region to replicate each copy to.
Simplio makes the copies
At the scheduled time it creates the snapshot in AWS and, if you asked for it, copies it to the other region. When there are more than you said, it deletes the oldest.
If a copy fails, it alerts you
An alert by email. A copy that isn't made is a problem you should know about the same day.
Restoring is a button
From the machine's snapshot list: create a new machine from that copy.
How secure it is
Deleting asks for two-factor
The copies that Simplio rotates on schedule are deleted according to the retention you set; deleting one by hand requires the code from your phone.
The copy in another region survives the region
A serious problem in one data centre doesn't affect copies held in another. It's the difference between a scare and losing everything.
Separate permission
Scheduling, creating or deleting snapshots are actions granted per person and per machine.
The same task, in AWS and in Simplio
| On your own in AWS | In Simplio | |
|---|---|---|
| Daily copy with retention | Data Lifecycle Manager: policy, tags on the machines, schedule, retention; per region | Schedule the machine: frequency and how many to keep |
| Copy in another region | Cross-region copy policy in DLM or AWS Backup, with its plan and its vault | A checkbox with the region |
| Know that the copy failed | Your own alarm on EventBridge events | Email alert |
| Restore | Console → snapshots → create instance → choose size, network, key… | "Restore" button on the copy |
Frequently asked questions
Do snapshots cost money?
Yes, AWS charges for the space they take up. That's why retention exists: Simplio deletes the old ones so you only pay for the ones you want to keep. The copy in another region takes up space there too.
Does it work for databases?
Lightsail and RDS databases have their copies from their own card. Scheduling with retention and replication is for machines.