AWS bedrock documentation change
Summary
Clarified that session tags appear in both classic CUR and CUR 2.0 for aggregated billing data
Security assessment
Change only provides billing clarification without addressing vulnerabilities or security controls
Diff
diff --git a/bedrock/latest/userguide/cost-mgmt-faq.md b/bedrock/latest/userguide/cost-mgmt-faq.md index 4665078f0..84d0a2e1a 100644 --- a//bedrock/latest/userguide/cost-mgmt-faq.md +++ b//bedrock/latest/userguide/cost-mgmt-faq.md @@ -84 +84 @@ The computed figure is an estimate. It does not reflect discounts, commitments, -A: Binding and destination. A session tag is set once at `sts:AssumeRole` and is constant for every call made with that session's credentials; it surfaces only as aggregated billing data in AWS Cost Explorer and CUR 2.0. Request metadata is set per call, varies per request, and lands in your invocation logs. +A: Binding and destination. A session tag is set once at `sts:AssumeRole` and is constant for every call made with that session's credentials; it surfaces only as aggregated billing data in AWS Cost Explorer and CUR (both classic CUR and CUR 2.0). Request metadata is set per call, varies per request, and lands in your invocation logs.