Importance Of Customer Avatar

Understanding your ideal customer avatar (or client, or student — but I’ll be using client throughout this post for brevity’s sake!) is key to the success of your business. When you intimately…

Smartphone

独家优惠奖金 100% 高达 1 BTC + 180 免费旋转




Automating EC2 Volume Snapshot creation in AWS

We are stopping EC2 instance(s) using CloudWatch schedule rule based on a tag key called snapshot. After the instance is stopped, we are creating root volume snapshot of the instance and when root volume snapshot process is completed then we start snapshot process for other attached volume(s) and also we start the instance as we don’t have to wait for other volume(s) snapshot process to be completed.

Every day at a certain time it will trigger a lambda function to stop EC2 instances.

Steps to create this rule:

If an EC2 instance is stopped, it will trigger a lambda function to create attached root volume snapshot.

Steps to create this rule:

If an EC2 snapshot is created successfully, it will trigger a lambda function to start the instance and create attached other volume(s) snapshot.

Steps to create this rule:

If an EC2 snapshot creation is failed, it will trigger a lambda function to send email to notify about the failure task and start instance.

Steps to create this rule:

Note: You have to add created Topic ARN in lambda function code.

Now that we have learnt how to create EC2 volume snapshot automatically. How do we restore volume from that snapshot? If you know the solution then post it as a comment on this blog.

And stay tuned, for my next blogs..

Add a comment

Related posts:

The Things We Consume End Up Consuming Us

Throughout my thirty years on this earth, I’ve had just about every bad habit imaginable. I’ve drank too much, struggled with addiction, gambled recklessly and have smoked a pack of cigarettes just…

Sebuah Kisah Antara Saya dan VIM

Akhirnya saya mulai menulis di Medium juga, setelah mengumpulkan cukup banyak niat yang lebih banyak nundanya dari pada mulainya. Dan entah kenapa saya mulai dengan tulisan ini. Soo… karena ini…