This article is tagged as relating to "AWS Backup" but describes its more rudimentary and limited predecessor service, Amazon Data Lifecycle Manager (DLM), instead. As a rule, I would recommend using AWS Backup as a much more advanced service and only resorting to the legacy DLM in specialised situations requiring it, such as when starting to use a newly opened AWS region that doesn't yet offer AWS Backup. I also suggest you retag the article for "Amazon Data Lifecycle Manager" and remove the misleading "AWS Backup" tag.
AWS Backup has massive benefits over DLM. As an important example, backup recovery points created of EC2 instances or EBS volumes via AWS Backup otherwise work as regular AMIs and EBS snapshots, able to be used the same way as any AMI or EBS snapshot, but as a prominent difference, those AMIs or snapshots cannot be deleted directly via the EC2 APIs. They can only be deleted via AWS Backup, making it much easier to use IAM policies to control who can delete backups, making it easy to provide powerful protection against inadvertent or malicious deletions of backups.
As another notable benefit, for typical operational purposes, also manually initiated backups/snapshots are advisable to create via AWS Backup. This makes manual operational work easier by allowing a retention time to be specified for each backup (recovery point) created via AWS Backup. If you specify a retention time of 14 or 35 days, for example, AWS Backup will automatically delete the snapshots and AMI when the retention time has elapsed, without requiring any custom Lambdas, manual reviews, or anything else beyond the standard AWS Backup service to leverage.
By comparison, a manual AMI or EBS snapshot created via the EC2 console will linger in the account forever, unless someone manually deletes them or builds custom code to help, contrary to the general best practice of using standard, cloud-native services when they're available.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr