EBS-SnapShooter – Python script to snapshot EBS volumes
github.com
github.com
I've also seen people use Lambda, which is halfway to "do AWS tasks with AWS's tools"; it's only a few lines of code and can be flexibly triggered without this much bulk. (Same code can usually be tossed in cron.)
If you want to go the persistent-daemon approach, there's something like automated-ebs-snapshots (which I used before CloudWatch Events came along), which is reasonably bulletproofed and is already used in anger: https://github.com/skymill/automated-ebs-snapshots
Writing stuff like this is decent practice to get comfortable with the AWS APIs, but these are generally solved problems. I'd be real uncomfortable with k8s's "secrets? what's that? is that something I store unencrypted?" approach to anything remotely sensitive when I'm throwing AWS credentials around; AWS already provides a better ACL method for this sort of thing in IAM. (If you have insisted on a k8s cluster and you aren't able to leverage IAM, this is a problem on your end that should be rectified sooner than soon.)
Part 1: create snapshots
https://serverlesscode.com/post/lambda-schedule-ebs-snapshot...
Part 2: expire old snapshots
https://serverlesscode.com/post/lambda-schedule-ebs-snapshot...
For this reason, for my backups, I run a cronjob on the EC2 instance and call fsfreeze (https://linux.die.net/man/8/fsfreeze). Is this unnecessary?
Here's my AWS Lambda implementation that snapshots and purges - https://github.com/manojlds/ebs-snapshot-lambda
It's an OpenSource project so feel free to contribute :)
(I will admit: am being a little hard on you because I think this is a bad idea. On the scale of bad ideas, it's only a bad idea and not a really bad idea, but it's a bad idea.)