You are often given the option to add tags to objects created in Amazon Web Services (AWS). It is easy to accumulate many objects in AWS. Tagging can help you locate specific objects.
However, tagging can also be used to create resource groups.
Resource groups are, like their name suggests, a logical grouping AWS resources. Imagine an administrator creating a series virtual machines (VMs), that all had to do with a particular project. Administrators might create a resource group that contains the project’s virtual machines (VMs) and related resources like load balancers and snapshots.
Administrators can add objects to a resource groups using tags and tag value. For example, an administrator might choose to create a resource group that includes all objects that include a particular tag. Administrators might need more control. They could create a resource group that is based on not only the tag but also the value of the tag. However, AWS supports tags for almost all object types. Not all object types can be included within a resource group.
It is easy to create a resource group. Log in to AWS console, then click on the Resource Groups link. The Resource Groups link isn’t located in the list, but instead appears in the black bar at top of the console. This is illustrated in Figure 1.
[Click on the image to see a larger version.] Figure 1: Click the link for Resource Groups. Click on the Create Resource Group option from the drop-down menu. You will be taken to the Create a Resource Group Page. Figure 2 shows how it looks. You will need to enter several pieces information on this page.
[Click on the image to see a larger view.] Figure 2: This interface is used to create a resource groups. As you might expect, the first step to creating a resource groups is to give it a name. Next, you will need to choose a tag that you want to associate with the resource groups. Look closely at Figure 2. You will see that the Tags field has a drop-down menu. Clicking on the arrow will reveal a list with all the tags currently being used in your organization. You can then choose from the list.
Next, you’ll need to choose a value to your chosen tag. This step can be a bit tricky because there are three options. Look at Figure 2. You will see that the field labeled Tagged with Any Value is just to the right. This default value is for this field and will ignore tag values. A matching tag is required for a resource that is to be included in the resource groups. The tag values don’t really matter.
You can also specify that the tag is empty. This is useful if you have multiple tags that have been assigned different values. You only want to include objects in the resource groups if their specific tag does not contain a corresponding value.
You can also enter a value. AWS will know that objects are only included in the resource groups if they have a matching value and a matching tag tag.
You don’t need to do anything if you want any value to be allowed to be used with your tag. Click on the value field to enter a value or to specify an empty one. This will display your existing tag values, and give you the option to use an empty one as shown in Figure 3. AWS also allows you to specify multiple tags for a resource category.
[Click on the image to see a larger version.] Figure 3: