AWS Snapshots and AMI Live | Data Life Cycle Live 🔴 | Cross Account Transfer Live| |in Hindi / Urdu
16#awsami #awssnapshot #aws
AWS Snapshots and AMI |Data Life Cycle Manager| Cross Account Transfer|
Use Amazon Data Lifecycle Manager (Amazon DLM) to automate the creation, retention, and deletion of snapshots taken to back up your Amazon EBS volumes. Automating snapshot management helps you to:
- Protect valuable data by enforcing a regular backup schedule.
- Retain backups as required by auditors or internal compliance.
- Reduce storage costs by deleting outdated backups.
Combined with the monitoring features of Amazon CloudWatch Events and AWS CloudTrail, Amazon DLM provides a complete backup solution for EBS volumes at no additional cost.
Understanding Amazon DLM
----------------------------------------------
The following are the key elements that you should understand before you get started with Amazon DLM.
Snapshots
-----------------
Snapshots are the primary means to back up data from your EBS volumes. To save storage costs, successive snapshots are incremental, containing only the volume data that changed since the previous snapshot. When you delete one snapshot in a series of snapshots for a volume, only the data unique to that snapshot is removed. The rest of the captured history of the volume is preserved.
Lifecycle Policies
----------------------------
Lifecycle policies consist of these core settings:
Resource type—The AWS resource managed by the policy, in this case, EBS volumes.
Target tags—The tags that must be associated with the EBS volumes to be managed by the policy.
Schedule—Defines how often to create snapshots and the maximum number of snapshots to keep. Snapshot creation starts within an hour of the specified start time. If creating a new snapshot exceeds the maximum number of snapshots to keep for the volume, the oldest snapshot is deleted.
For example, you could create a policy that manages all EBS volumes with the tag account=Finance, creates snapshots every 24 hours at 0900, and retains the five most recent snapshots. Snapshot creation could start as late as 0959.
The following considerations apply to lifecycle policies:
- A policy does not begin creating snapshots until you set its activation status to enabled. You can configure a policy to be enabled upon creation.
- Snapshots begin to be created by a policy within one hour following the specified start time.
- If you modify a policy by removing or changing its target tags, the EBS volumes with those tags are no longer affected by the policy.
- If you modify the schedule name for a policy, the snapshots created under the old schedule name are no longer affected by the policy.
- You can create multiple policies targeting the one or more EBS volumes, as long as distinct tags are used by each policy. Target tags cannot be reused across policies, even disabled policies.
If an EBS volume has two tags, where tag A is a target of policy A to create a snapshot every 12 hours, and tag B is a target of policy B to create a snapshot every 24 hours, Amazon DLM creates snapshots according to the schedules for both policies.
- When you copy a snapshot created by a policy, the retention schedule is not carried over to the copy. This ensures that Amazon DLM does not delete snapshots that should be retained for a longer period of time.