Component cost-allocation tag on every stack - #55
Merged
Conversation
One loop before app.synth() tags each stack with Component = its suffix in the deployment contract (expected_stacks vocabulary), covering use-case stacks and any future stack for free. README documents activation (ce update-cost-allocation-tags-status) and the honest scope: resource costs only — AgentCore Memory/SSM params take no CFN tags, and Bedrock inference attribution needs Application Inference Profiles (own task). Verification: ruff clean; pytest 194 passed; check-contract.sh all 6 presets PASS; synth shows Component on orchestrator stack resources and confirms memory stack resources were never taggable (no Project tag either, pre-existing).
|
Commit: Security Scan Results
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Roadmap R3 phase 1: every stack gets a
Componenttag (its suffix in the deployment contract —gateway,memory,runtime-orchestrator, use-case stacks included), so Cost Explorer can split spend per component once the tag is activated. One loop in app.py before synth — no per-stack edits, future stacks tagged for free.Changes
Verified
Component: runtime-orchestratoron taggable resources; memory template has no tags at all — confirmed pre-existing (it never carried the global Project tag either; AWS::BedrockAgentCore::Memory and SSM parameters accept no CFN tags).Review notes