Bedrock Agent costs not showing Application Inference Profile tags in Cost Explorer

Question

Hi!
I am trying to get detailed cost information for my Bedrock agents to understand how much each agent costs individually. After reading the documentation, I understood that setting tags at the agent level is not sufficient for cost tracking, so I implemented the following approach:

**What I implemented:**
* Created Application Inference Profiles (one per agent) with detailed tags including: Agent, Model, Use, Region, etc
* Attached each Application Inference Profile to its corresponding Bedrock agent
* Activated all relevant tags in "User-defined cost allocation tags" in the billing console
* Also added tags directly to each agent as an additional attempt

**Current status:**
*  It has been 48+ hours since implementation
* Tags do not appear in Cost Explorer for agent usage
* I have confirmed that Cost Allocation Tags are activated and showing as "Active" status
* Direct model invocations using the same Application Inference Profiles DO show tags in Cost Explorer correctly
* Only Bedrock Agent invocations fail to show tag attribution

**Technical details:**
* Agents are using Application Inference Profiles with ARN format: arn:aws:bedrock:REGION:ACCOUNT:application-inference-profile/PROFILE_NAME
* Profiles are wrapping system-defined inference profiles (e.g., us.anthropic.claude-3-5-haiku-20241022-v1:0)
* Agent status shows as "PREPARED" and functioning normally
* Region: us-east-1

**Expected behavior according to documentation:**
Application Inference Profiles should enable cost tracking for both direct model calls AND Bedrock agent usage, with tags appearing in Cost Explorer.

**Actual behavior:**
* Direct model calls with Application Inference Profiles → Tags appear in Cost Explorer
* Bedrock Agent calls using Application Inference Profiles → Tags do NOT appear in Cost Explorer

**Question:**
Is this expected behavior, or is there a configuration step I'm missing? Should Bedrock Agent costs inherit tags from their attached Application Inference Profiles, or is this a known limitation?

Any guidance would be greatly appreciated!"

re:Post Agent · Answer

Based on the information available, there are several potential reasons why your Bedrock Agent costs are not showing Application Inference Profile tags in Cost Explorer:

1. Time delay: While you've waited 48+ hours, in some cases it can take longer for newly activated cost allocation tags to appear in Cost Explorer. The activation process can take up to 24 hours to complete and for the tag data to appear, but in practice, it sometimes takes longer.

2. Tag application: There might be a difference in how tags are applied between direct model invocations and agent invocations. Since you're seeing tags work correctly for direct model invocations but not for agent invocations, this suggests a potential limitation in how the tagging system works with Bedrock Agents specifically.

3. Resource charges: Cost Explorer will only show tags for resources that have actually incurred charges. If your Bedrock Agents haven't generated significant costs yet, this could affect tag visibility.

4. Tag activation: While you've confirmed that your cost allocation tags are activated, it's worth double-checking that the specific tags used for the Bedrock Agents are properly activated in the Billing and Cost Management console under Cost Allocation Tags.

To troubleshoot further:
- Verify that the Application Inference Profiles are correctly attached to your agents
- Check if there are any specific tagging requirements or limitations for Bedrock Agents that differ from direct model invocations
- Consider creating a test case with higher usage volume to ensure costs are significant enough to appear in reports
- If the issue persists, you may need to contact AWS Support as this could be a limitation with how Bedrock Agent costs inherit tags from Application Inference Profiles

Since direct model invocations with the same Application Inference Profiles are correctly showing tags in Cost Explorer, this suggests there might be a specific limitation or configuration requirement for Bedrock Agents that isn't documented clearly.  
**Sources**  
[What are the reasons for Budget not working using cost filter with specific tags even after activating these tags in Cost Allocation Tags section ? | AWS re:Post](https://repost.aws/questions/QU51YYXUsFSN-FUZ4H9dkqEw/what-are-the-reasons-for-budget-not-working-using-cost-filter-with-specific-tags-even-after-activating-these-tags-in-cost-allocation-tags-section)  
[Activate cost allocation tags associated with the solution - Modular Cloud Studio on AWS](https://docs.aws.amazon.com/solutions/latest/modular-cloud-studio-on-aws/activate-cost-allocation-tags.html)

Bedrock Agent costs not showing Application Inference Profile tags in Cost Explorer

Add your answer

Relevant content