[Feature Update]: Now Avoid Accidental Deletion of Old Resources with AWS Tagging Strategies
In our previous blogs, Key AWS Tagging Strategies To Live By, and 5 Effective Tagging Strategies For AWS Cloud Cost Allocation, we highlighted the importance of tagging principles. Without a doubt, AWS Tagging Strategies is pivotal in streamlining the cloud resources across teams and business units. By doing so, hundreds and thousands of cloud resources can be managed at the tip of the fingers in a very short duration. Especially as a business scales-up.
On the flip side, without a proper tagging strategy in place, it becomes very challenging. This could lead to various problems ranging from operational issues and unexpected cloud spends to accidental deletion of key resources.
Many of our customers continually share their experience about AWS — and they love the tagging feature in it. They talk about how beneficial it has been for them to classify their resources in multiple ways. For instance, they could categorize the AWS resources by purpose, possessor, or situation and then assign the tags.
Few customers love the way how keys could be defined with optional values to each tag. They like the way they could pre-define a set of tags for an Amazon EC2 instances and track each instance’s owner at the stack level.
When we asked these customers what they liked and disliked about Botmetric — and its tagging related features in particular? We got many responses. And they were happy about how Botmetric performed DevOps automation task with dexterity and enabled them to set customized audit preferences based on tags. However, few of them showed concern about accidental deletion of old EBS snapshots.
Just to set the context here: Botmetric lists all the old resources such as AWS EBS Snapshots and AMIs that are 90 days old while performing audits. By default, these old resources are either deleted or de-registered depending upon whether they are EBS snapshots or old AMIs and so forth. Why because, they are directly related to cost reduction.
In majority of the cases, these 90-days old snapshots and AMIs are of no use. In few cases, however, they might be of use even after 90 days depending on the business needs.In such cases, an accidental deletion of these resources might occur affecting the businesses backup needs.
This accidental deletion of 90 days old resources was one of the concerns for our customers. Catering to this need, we at Botmetric created a way to avoid this scenario using the AWS tagging principle.
The Way Forward: Leveraging AWS Tagging Principle
For Botmetric to not act upon the old useful resources, user needs to first add ‘PRESERVE_RESOURCE’ as a tag-key to all these resources.They are also required to give the tag-value as the user thinks is appropriate. By doing so, the Botmetric will sieve all those old resources with the ‘PRESERVE_RESOURCE’ tag-key during the next audit cycle and avoid accidental deletion of necessary resources despite being 90-days old.
Here is a list of few jobs in the audit cycle where users can make use of the ‘PRESERVE_RESOURCE’ tag, and avoid accidental deletion of old resources in the future:
- Creating EBS Snapshots based on Instance Tags
- Creating EBS Snapshots based on Volume Tags
- Creating EBS Snapshots based on Instance Ids
- Copying EBS Snapshots across accounts based on volume tags
- Copying EC2 AMI across accounts based on AMI tags
- Copying EC2 AMI across regions based on AMI tags
- Creating EC2 AMIs based on Instance tags
- Deleting Old EBS Snapshots
- De-registering Old EC2 AMIs
- Creating RDS Snapshots based on the DB Instance tags
- Copying RDS Snapshots based on DB Snapshot tags
- Creating Redshift Snapshots based on DB cluster tags
To Wrap Up
Tags enable AWS users to categorize AWS resources in different ways. It helps users to search and filter the resources based on the tags. And a consistent set of tag keys makes users life easier to manage AWS resources, thereby contributing towards optimization of the AWS for cloud cost.
The beauty of Botmetric cloud management suite is that it not only helps AWS users to perform DevOps tasks by creating scheduled jobs and help manage it, but also avoids accidental deletion of useful old resources.
We at Botmetric are continually improving our product based on the feedback from our customers. We’d love to hear from you too. Until we come-up with our next blog, do keep in touch with us on Facebook, Twitter, and Linkedin.
This special product feature update blog is written by our Technical Architect, Yuvaraj Loganathan. To Listen to his webinar session on ‘Art of Reservation’, click here.
Latest posts by Rajeev Kumar (see all)
- Dynamically Increase AWS EBS Capacity On-the-Go Now with New Elastic Volumes - February 16, 2017
- Top 11 Hard-Won Lessons We’ve Learned about AWS Auto Scaling - January 16, 2017
- AWS For E-Commerce & Online Retailers: Sky’s The Limit. Agree? - October 17, 2016