Add AWS cost allocations tags on all deployed resources consistently so that we can generate detailed cost reports in Kion

[mike-gangl]

By doing this, tenants will be able to log in to Kion and use these tags in cost reports to see detailed cost reporting by environment, service area, and capability. for example, A tenant can find all dev costs for the SPS system. OR how much does running the ADES in Test cost them.

By doing this, we can also have the service areas be able to tell us expenditure information each PI for each venue to which they are deployed.

• ADE costs (Jupyter, worker nodes, EFS/EBS)
• SPS costs (Always on cost, scaled worker costs)
• UAS costs SDAP Cluster costs

Acceptance Criteria

• Updated guide on tag mappings (UCS)
• Tags added to deployed resources (by environment) (all)
• Tags added to automated deployment resources (by environment) (all)
• Jobs to report non-appropriately tagged instances (UCS)

GUIDANCE: https://unity-sds.gitbook.io/docs/developer-docs/common-services/docs/users-guide/deployment/unity-aws-resource-tagging-conventions

[mike-gangl]

UCS probably plays a part of this, enforcing tagging in MCP so that we can get cost by service areas.

[mike-gangl]

Cost tags that work in MCP:

Tag key

CreatedBy Customer Env mcpBilling mission Name Proj ServiceNow Instance Stack station

[rtapella]

Currently UI not intended to make a new cost-dashboard type of UI. I would expect this to be in AWS/MCP (?). We can link to it in the common navigation

[mike-gangl]

@rtapella we can discuss linkages; it's in the MCP dashboard (kion) which may or may not make sense to link to depending on who has access to it. i believe Ruth mentioned wanting to see these things, so access at some level is expected.

[galenatjpl]

@mike-gangl please share this ticket with @buggtb @ramesh-maddegoda @ryanhunter-jpl @jonathansmolenski

[galenatjpl]

@mike-gangl Probably obvious, but an additional acceptance critieria is to run and view a cost report in Kion