Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions,
see Getting Started with Amazon Web Services in China
(PDF).
Tagging categories
Companies that are most effective in their use of tags typically create
business-relevant tag groupings to organize their resources along technical, business,
and security dimensions. Companies that use automated processes to manage their
infrastructure also include additional, automation-specific tags.
| Technical tags |
Tags for automation |
Business tags |
Security tags |
-
Name – Identify
individual resources
-
Application ID – Identify
resources that are related to a specific application
-
Application Role –
Describe the function of a particular resource (such as web
server, message broker, database)
-
Cluster – Identify
resource farms that share a common configuration and perform
a specific function for an application
-
Environment – Distinguish
between development, test, and production resources
-
Version – Help
distinguish between versions of resources or
applications
|
-
Date/Time – Identify the
date or time a resource should be started, stopped, deleted,
or rotated
-
Opt in/Opt out – Indicate
whether a resource should be included in an automated
activity such as starting, stopping, or resizing
instances
-
Security – Determine
requirements, such as encryption or enabling of Amazon VPC flow
logs; identify route tables or security groups that need
extra scrutiny
|
-
Project – Identify
projects that the resource supports
-
Owner – Identify who is
responsible for the resource
-
Cost Center/Business Unit
– Identify the cost center or business unit
associated with a resource, typically for cost allocation
and tracking
-
Customer – Identify a
specific client that a particular group of resources
serves
|
|