AWS Adds Support for Tagging Amazon EBS Snapshots Upon Creation and Resource-Level Permissions

tagging amazon ebs snapshots

In previous blogs, we have explained why properly tagging AWS resources is necessary, and we have explored some of best practices and recommended strategies for applying tags for your AWS cloud environment. Amazon Web Services have now taken this further and provided some great new support features for tagging Amazon EBS Snapshots so you can exercise more control them. You can now tag your Amazon Elastic Block Store (Amazon EBS) Snapshots at the time of creation. You can do this from the Amazon EC2 console or through the CreateSnapshot API. By tagging resources at the time of creation, you can eliminate the need to run custom tagging scripts after resource creation.

Set Resource-level Permissions

In addition, you can now set resource-level permissions on the CreateSnapshot, DeleteSnapshot, and ModifySnapshotAttribute APIs. This allows you to implement stronger security policies by giving you more precise control over actions that users and groups can take over specific snapshots. You can also enforce the use of tagging and control which tag keys and values are set on your resources.

With these new features, you can exercise much more control over your Amazon EBS Snapshots, track them easily by tagging EBS snapshots upon creation, and achieve more accurate cost allocation reporting. These new features are provided at no additional cost. To learn more, see EC2 User Guide for tagging your resources and working with Snapshots for applying resource-level permissions to Amazon EBS Snapshots.

Tagging Amazon EBS Snapshots and Cost Allocation 

One of the key features of tagging Amazon EBS snapshots is that it makes it easy to run detailed billing reports on specific resources. The AWS Cost Explorer can run cost allocation reports based on any tag, allowing users to get a detailed look at the cost of specific resources. Keep in mind that because AWS allows up to 50 tags per resource, these strategies are not mutually exclusive, and can easily be run in conjunction with one another.

Tagging And CloudRanger

While tagging AWS resources is an important step, Amazon’s native console still requires some scripting when managing the mundane but necessary processes such as scheduling EC2 instances or routine daily Amazon EBS volumes snapshots. With, CloudRanger’s simple, user-friendly console, we make it easy to schedule these routine tasks by tag without the need for an IT professional. CloudRanger provides an easy-to-use, scalable platform for snapshot and AMI management of Amazon EC2, RDS and Redshift resources utilizing AWS native snapshots. Simply choose your schedule, set a retention period and apply by tag or instance ID for each of your backup policies or server schedules. By applying custom resource tags to your chosen actions in CloudRanger, this provides an easy-to-use, cost-efficient solution for managing high volumes of Amazon EC2 and RDS resources, saving your team time, money and the hassle of managing scripts or performing manual tasks.

Tagging CloudRanger

Try CloudRanger For Free

Whether you are a small business, a medium business, or an enterprise user of Amazon Web Services, CloudRanger has features that will meet your needs. Our AWS backup, recovery and server scheduling platform is easy to setup, which means your business can be up and running with CloudRanger in no time. And best of all, you can even try CloudRanger for free for 14 days. So why not experience all the money-saving features and time-saving benefits CloudRanger has to offer?

Steven

This entry has 0 replies

Comments are closed.