A technician copies EBS snapshots to another Region with a script on a laptop. The copies stop whenever that laptop sleeps or leaves the network. How should the cross-Region copy run instead?
Select an answer to reveal the explanation.
Short Explanation
The laptop script is a courier who only travels while that laptop is awake. You move the cross-Region snapshot copy into the AWS Backup plan so the copy runs without the laptop. A bigger laptop is still the same courier.
Full Explanation
The laptop script copies snapshots only while that computer is on and online, so the cross-Region copy stops when the machine sleeps or leaves the network. AWS Backup can copy recovery points to a vault in another Region as part of the backup plan that already protects the volumes. Putting the copy in that plan makes it an action AWS runs, instead of a job tied to one laptop. Moving the laptop to the destination Region still ties every copy to one workstation. A larger laptop fails the same way when it sleeps. Downloading a snapshot onto a disk and uploading it in the other Region's console is another manual courier path. Cross-Region snapshot copy belongs in the backup plan, not in a file carried on a laptop. Caveat: the destination vault has to exist in the other Region, and the backup role has to be allowed to write recovery points there, or the local backup can succeed while the copy fails. Operational check: run an on-demand backup and confirm a recovery point shows up in the destination Region vault while the laptop is offline.