MCM-20 — Custom Tag Improvements
Overview, personas, and architecture for the Custom Tag Improvements initiative — allowed-list reconciliation, resource-view editing, and topology-driven tag suggestions.
MCM-20 — Custom Tag Improvements
Custom Tags let an Enterprise govern a set of tag keys (with an optional allowed-values policy) and apply them consistently across discovered cloud resources for cost allocation, compliance, and reporting. This initiative closes several real gaps in that system: values that exist on resources but aren't in the allowed list are invisible today; the UI doesn't enforce the backend's 50-resource bulk-update cap; tags can only be edited from one narrow screen; and there's no resource topology to drive tag suggestions from, despite the product's own overview docs already describing one conceptually.
Known tagging bugs for specific AWS resource types (Key Pairs, IAM Users) are tracked as bugs, not as user stories, and are out of scope for this page.
Each user story below is a self-contained page with its own acceptance criteria, technical design, and UI changes. This page holds only what's shared across all of them.
Personas
| Persona | Role | Primary concern |
|---|---|---|
| Enterprise Admin | Owns the tag policy — defines tag keys and their allowed values, resolves values that fall outside policy | Consistent, clean tag data across the enterprise for cost/compliance reporting |
| Platform User | Discovers, inspects, and tags cloud resources day-to-day | Being able to tag resources correctly wherever they're working, without hitting silent failures or opaque limits |
System Context
The allowed-value policy and bulk tag update already live in the tagging & compliance capability, not the resource discovery capability, even though the Custom Tags UI is presented under Discovery — this initiative works within that existing ownership split rather than moving the capability.
User Stories
| Story | Summary |
|---|---|
| MCM-21 — Reconcile Tag Values Outside the Allowed List | Surface out-of-policy values and let an Admin migrate or allow-list them. |
| MCM-22 — Enforce the 50-Resource Cap in the Bulk Tag Update UI | Block over-selection in the UI instead of failing at the API. |
| MCM-25 — Add, Update, and Delete Tags from the Resource Detail View | Add, update, or delete a resource's tags without leaving its own detail page. |
| MCM-26 — Show Associated Resources in Resource Topology | Replace the "Coming Soon" topology view with a real one. |
| MCM-27 — Suggest Missing Tag Values from Resource Topology | Propose tag values based on what related resources already carry. |
| MCM-28 — Manage the Custom Tag Allowed List in Settings | Add/update/remove allowed values from the tag's own Settings tab. |
Cross-Cutting Non-Functional Requirements
| ID | Requirement |
|---|---|
| NFR-01 | Tag updates must remain tenant-scoped — a resource can only be tagged by a caller within its owning tenant, matching existing tenant-isolation behavior elsewhere in the system. |
Out of Scope
- Moving the Custom Tag / tag-update capability out of tagging & compliance and into resource discovery — this initiative works within the existing ownership split.
- Raising the 50-resource cap itself — the bulk-update-cap story only brings the UI in line with the existing server-enforced limit, it doesn't propose changing the limit.
- Resource-type-specific tagging bugs (e.g. AWS Key Pairs, IAM Users) — these are tracked as bugs, not as stories on this page.
MCM-46 — FinOps New Recommendation Notification
Notify when a new cost-saving recommendation is generated, with a "new" indicator that outlives the notification itself.
MCM-21 — Reconcile Tag Values Outside the Allowed List
Surface tag values that exist on resources but aren't in a tag's allowed list, and let an Admin migrate or allow-list them.