End of support notice: On June 30, 2027, AWS will end support for AMS Advanced. After June 30, 2027, you will no longer be able to access the AMS Advanced console or AMS Advanced resources. For more information, see AMS Advanced end of support.
AMS recommended tags
AMS recommends the following tags on supported resources. Starred (*) tags are highly recommended.
Note
You can use tags to schedule patching. For information, see AMS Advanced Patch Orchestrator: a tag-based patching model.
| Tag key | Supported values | Notes |
|---|---|---|
|
Unconstrained. |
Identify the applications that will reside on, or require access to, the resource. This facilitates tracking and communications between AMS and you. |
| ||
|
Distinguish between development, test, and production infrastructure as the environment for the resource. | |
|
Distribution list email address |
Identify the distribution list email address for the team responsible for the resource. The email should not be a personal email; it must be an anonymous email like a distribution list. |
|
Unconstrained |
Identify which controls and policies should be applied to the resource. |
|
Identify the cost center or business unit associated with a resource (typically for cost allocation and tracking). | |
|
Used by AMS customers that have resources from multiple customers (AMS sub-customers). To group resources in the managed environment into the specific customer they are serving. Identify a specific client on a particular group of resources or services. | |
|
Identify the specific data-confidentiality level a resource supports. Identify which controls and policies should be applied to the resource. | |
|
Identify the date or time a resource should be started, stopped, deleted, or rotated. | |
|
Identify the team responsible for the resource. Facilitates communication with the team responsible for the resource. | |
|
You have two options:
|
What resources to include in an automated patching maintenance window. |
|
Unconstrained |
Identify the projects the resource supports. |
|
One of six possible acronyms for Confidentiality, Integrity, or Availability; the order of the acronym is the priority. For example, I.C.A. would mean the order is Integrity, Confidentiality, Availability. Other acceptable values are C.I.A., C.A.I., I.A.C., A.C.I., and A.I.C. |
Identify which type of support should be priority: Confidentiality, Integrity, or Availability. |