| Tag Name (Key) | Description |
|---|---|
| Environment | Used to distinguish between production (prd), development (dev), and staging infrastructure (stg). Application Used to describe the set of disparate resources (or clusters) that work together to deliver a product or service to a customer. |
| Application | If this resource belongs to a application place the name of the application |
| Project | The project name that a group of instances and resources bellong, eg: mrsv4 |
| Cluster | Used to identify the set of instances that share the responsibility for perform a specific function as part of an application. Clustered instances typically share the same configuration and exist behind a load balancer. |
| Role | Used to describe the function of a particular node (web server, database server, load balancer, etc.). Instances within a cluster generally play the same role, but instnaces with the same role are not necessarily part of the same cluster or application (i.e. web server for app 1, web server for app 2). |
| Owner | Used to identify the individual or team who is responsible for the instance. Usually a AIM user or e-mail address |
| CostCenter | The charged department or company. eg: gpa |
| ExpiresAt | Optional. Defines a due date. |
| Options | Options. Get additional values like "Backup, Secure". |
| LegacyName | Legacy resource name used before it had been renamed |
Pattern:
[<CostCenter>-]<ProjectName>-<Role>-<Environment>-<AvailabilityZone>
Example:
owf-aem-prod-1a
Patter:
[<CostCenter>-]<ProjectName>-<DbType>-<DeploymentType>-<Environment>
| Tag Name | Example |
|---|---|
| DbType | oracle, mysql, postgres, maria, aurora |
| DeploymentType | az, single, slave |
Example:
owf-aem-mysql-az-prod