Introduction > Step 1 > Step 2 > Step 3
Located the Elastic Block Store section and click Lifecycle Manager.
You will either see the default landing page If this is what you see, keep the EBS Snaphot Policy selected, and hit Next
Or If you see the DLM table Selected the Create lifecycle policy button. Which opens the Select policy type screen. Scheduled-based policy and EBS snaphot policy is what you need…then hit Next
To create a DLM there are 3 steps. Specific settings -> Schedule -> Review.
There will be [at the time of writing this guide] 5 sections in this step.
Let’s walk through each.
The tag name should be unique to your node if you want to target only your node’s volume for a snapshot/backup.
Give your policy a sensible description. eg. Minima Daily DLM or Minima weekly DLM or what ever frequency you will be backing up.
The default is good enough for this guide; creating a specific role is beyond this guide but worth looking into if you want to follow leading practices like least privilege security model.
Again, default is good enough, but I like to add a Name tag with a sensible value.
Another default, which means the policy will go live immediately after completion.
This step is all about how often your snapshot will be performed. For my example I have selected:
The time is when it first kicks off. We will want to put that 10 - 15 minutes ahead of the current UTC. You can check that here
The last setting is the Rention value.
For my example I use a count of 1. Which means AWS will keep the last snapshot; when a new snapshot is taken an hour later, the old snapshot is automatically delete.
You can chose a different rention period if you like. Just remember snapshots cost money in AWS.
The other settings in the Configure schedule wizard are optional and beyond the scope of this guide.
Hit the orange Review button.
The last step is a review of your values. Double check the values and if you are happy hit the orange Create policy button.
You will now see a Data Lifecycle policy in the manager table.