How is Bedrock spending trending this month?
FinOps and Finance
Compare daily Actual and Estimated costs, then discuss reports with budget owners.
AI Lens for Bedrock
Track Amazon Bedrock requests, tokens and costs across accounts and regions, with user budgets, guardrails and team reports.
Turn requests across accounts into a shared view of tokens and costs. Keep estimates distinct from actual costs, and budget alerts distinct from guardrails.
Conceptual flow, not a deployed-system topology
Purpose-built views for costs, tokens and administration.
Compare Actual from AWS Cost Explorer with Estimated from tokens × on-demand prices, alongside model and owner costs.
Different data sources; estimates may differ from billed costs.
Review input, output, cache read and cache write tokens, daily averages and cache share when investigating costs.
Cache read + write ≈ 97% of example tokens.
Review Bedrock usage across AWS accounts and regions, with request counts separated by operation.
Export Cost by user, Daily cost summary and Model usage summary for finance or product discussions.
Bring summaries into team reports and reviews.
Choose daily, weekly or monthly UTC periods and email alerts through Amazon SES at 80% and 100% of the configured budget.
Illustrative alert state; no email is sent.
Manage Bedrock Guardrails and account-level enforcement by region, including Asia Pacific (Thailand). Review blocked-event Guardrail Logs without showing prompts or model responses in that log view.
Guardrail Logs omit prompts/responses in this log view.
Create IAM users and API keys, email newly issued keys to their owners, and deactivate or delete callers when needed. These are separate from dashboard accounts.
New keys are emailed to owners through the product workflow.
Manage dashboard accounts and groups through Amazon Cognito, with configurable TOTP authenticator MFA.
Dashboard accounts are separate from model-calling IAM/API keys.
Illustrative team scenarios, not customer testimonials.
How is Bedrock spending trending this month?
Compare daily Actual and Estimated costs, then discuss reports with budget owners.
Which service calls models most?
Review callers, services, models and operations across connected accounts and regions.
How is our chatbot usage changing?
Follow active members and conversations, with changes from the previous period.
Assess connections and permissions with the team before using real data.
Identify a use case, connected accounts, owners and permissions to assess.
Review Invocation Logs, Cost Explorer and tags used to identify cost owners.
Review user budgets, guardrails and reports, validating scope before rollout.
| Data sources | Bedrock Model Invocation Logs and AWS Cost Explorer; iamPrincipal/Owner tags |
|---|---|
| Operations | InvokeModel, InvokeModelWithResponseStream, Converse, ConverseStream |
| Cost calculation | Actual from Cost Explorer; Estimated from tokens × on-demand prices can differ from billed costs |
| Budget periods and alerts | Per user; daily/weekly/monthly (UTC); 80%/100% thresholds; Amazon SES |
| Guardrail regions | US East (N. Virginia), Asia Pacific (Singapore), Asia Pacific (Thailand), per supplied document |
| User accounts | Bedrock callers: IAM/API key; dashboard users: Cognito/TOTP MFA |
AI Lens for Bedrock
Talk to eCloudvalley for a demo and an assessment of your AWS account connections.