#Tag editor aws update#
#Tag editor aws download#

Good news: they don't cost anything.Īnd as an added bonus, you can export the results as a CSV file. that get allocated by default even though you may not use them. A lot can be related to VPC subnets, etc. It is slow to begin with, and in one case where I have a single EC2 instance and a few ancillary items like a git repository, I have 190 resources allocated. You are probably using a lot more AWS resources than you think, so I don't recommend the 'All supported resources' option. If you want to enumerate all your EC2 instances everywhere, select 'All regions', 'AWS::EC2::Instance' (you can type 'instance' and it will give you matching choices), and leave the Tags section blank. You can choose a specific resource type, or 'All supported resources', then narrow your search by tags. The Tag Editor itself provides a search engine where, while selecting a region, you call specify 'All regions'… Here you can create groups of resources based on tags or CloudFormation stacks and mass-edit tags on resources that share something in common. But just before I was about to embark on this spelunking adventure, which would have cost me time writing and debugging, I stumbled upon a useful search feature where you probably haven't looked before.įrom the main menu or search find 'Resource Groups & Tag Editor'. If you are a scriptwriter, like I am, you'd probably be tempted to write a script that used the AWS API to do this automatically, iterating over the regions. If you were tasked with enumerating all your EC2 instances worldwide, you'd probably have to go to the region pulldown and get a list for each region - 21 of them at the time of writing. For the most part, the AWS Management Console only provides information on a given region.

#Tag editor aws update#

That’s it! Click, search, update and you are done.If you have a lot of resources in AWS spread across multiple regions, sometimes it can be cumbersome trying to remember which resources are in each region. Once you have all of your infrastructure following your tagging policy, make sure to implement some automation to enforce your policy. You will then be able to see all tags for each resource of that search.

#Tag editor aws download#

You may also want to click on the download icon and select option “Export all columns” before updating all of your resources. Finally, click on “ Apply changes.” There is no way to “undo” so make sure that you take your time.(Ex: Tags: Team, Value: Not tagged.) This will filter out the resources that are already tagged. A workaround, is to tell the initial search not to include the already tagged resources. If you change it to a new value, it will remove old values for all of the selected resources. If there are multiple resources with different values for the same tag, you will see “ Multiple values.” Again, be careful. Note, the screen shows your existing tags. Click on “ Edit Tags for selected” and add/update the tags for all of the selected resources.This is actually the only place in the console where you can see and download a list of all of the resources that you have from all regions… Notice the download icon on the top right of the table, it allows you to download a csv of all of your resources with their current tags. Be carful not to blindly select everything. Select the resource you like to update.Useful options include “ contains, not tagged and empty value” where you input the tag values.

For the resource types, I would recommend to start with the most important EC2 Instances. Enter the regions that you would like to lookup resources in. Login to your console and click on “ Resource Groups” then “ Tag Editor“.Simply use the AWS Console Tag Editor that is already available with your AWS console. Here is a very easy way to get your tagging under control.