Import YAML Runbook as an AWS Systems Manager Automation Document to Delete Unattached EBS Volumes

“ I have checked the documents of AWS to import yaml runbook as an aws systems manager automation document to delete unattached ebs volumes. AWS systems manager makes it easy and secure for runbook import as yaml and run it for deletion activity with version control and follow flow steps in runbook. In terms of cost, the solution is cheaper and secure.”

AWS Systems Manager helps you centrally view, manage and operate nodes at scale in AWS, on-premises and multicloud environments. With the launch of a unified console experience, systems manager consolidates various tools to help you complete common node tasks across AWS accounts and AWS regions.

In this post, you will experience import yaml runbook as an aws systems manager automation document to delete unattached ebs volumes. Here I have imported the yam file in runbook for ssm document creation and then executed the automation runbook to identify, list, approve and delete the unattached ebs volumes.

Architecture Overview

The architecture diagram shows the overall deployment architecture with data flow, aws systems manager, iam role, iam user, ebs volume, amazon ec2, documents.

Solution overview

The blog post consists of the following phases:

1. Create of SSM Document as Runbook in AWS Systems Manager
2. Output of Executing Automation Runbook for Deletion of Unattached EBS Volumes

Phase 1: Create of SSM Document as Runbook in AWS Systems Manager

1. Open the AWS Systems Manager console, goto documents option under change management tools and create an automation document as create of runbook from yaml file with import runbook option. We can see the flow diagram once the import is completed as the steps of flow mentioned. The parameters are present where we need to give input value during the runbook execution initiation. Once the document creation completes, we can see the document under owned by me option in the document tab. Whenever we need to have an updated yaml file in runbook, we can create a new version as a default one with a new changed yaml file. Make sure to make the version as default else it will not execute the current changed yaml file.

Phase 2: Output of Executing Automation Runbook for Deletion of Unattached EBS Volumes

Clean-up

AWS systems manager : documents, iam role, ec2 instance, ebs volume and iam user.

Pricing

I review the pricing and estimated cost of this example.

Cost of Amazon Elastic Compute Cloud = $0.05

Cost of Systems Manager = $0.00
[ AWS Systems Manager AWS-Auto-ScriptDuration-Tier3 for 22000 units = $0.00
AWS Systems Manager AWS-Auto-Steps-Tier1 for 52 steps = $0.00 ]

Total Cost = $0.05

Summary

In this post, I showed “import yaml runbook as an aws systems manager automation document to delete unattached ebs volumes”.

For more details on AWS Systems Manager, Checkout Get started AWS Systems Manager, open the AWS Systems Manager console. To learn more, read the AWS Systems Manager documentation.

Thanks for reading!

Connect with me: Linkedin