AWS Bedrock

Connection steps for the daily pull are in the Bedrock connector guide. This page is how those dollars, and a FOCUS upload of the same spend, get a department and an agent.

There are two paths. They answer different questions. Cost Explorer is the daily total. The FOCUS upload is what carries tags.

What you set up

Daily total. Connect AWS Bedrock with the connector guide. Cost Explorer credentials need permission to read cost and usage. That pull has no tags to configure.

Tags, when you want a department or an agent.

1. Call models through an application inference profile, not by model id alone. One profile is one model. A workload that calls several models needs one profile per model, carrying the same keys. (Application inference profiles)
2. Tag each profile. Meridian's defaults are a cost-center key of CostCenter, Department, or cost-center, and an agent key of Agent. Those are not the OASA keys. See tagging.
3. Activate the tag keys as cost allocation tags in AWS Billing. Tags apply to cost incurred after activation. A backfill of up to 12 months is available only for months the resource already had the tag. (Activating tags, backfill)
4. Create the department under Governance, with a code or name that matches the tag value. Create the agent under Agents & allocation with a name that matches the Agent tag. Meridian does not create the agent from the tag.
5. Upload the AWS FOCUS-format Cost and Usage export on Uploads. An optional account-to-department crosswalk on that form can set a department when the row has no matching tag.

While the Cost Explorer connector is connected, Bedrock rows in a FOCUS upload are held. The upload tells you to resolve that reconciliation item before choosing a source of record. The hold is there so the daily total and the tagged lines are not both booked.

What Meridian receives

Cost Explorer. One charge per UTC day for Amazon Bedrock. Meridian asks Cost Explorer for usage type, then adds those amounts into a single daily total. Token counts are zero. Tags are not requested. (GetCostAndUsage) Cost data can lag by a day or two.

FOCUS upload. One row per line in the file you upload. For Bedrock that line can name the inference profile and the cost-allocation tags AWS copied onto it. Meridian accepts FOCUS 1.2 and 1.3, and is forward-tolerant of 1.4 columns. The inference profile ARN is not used as the agent.

How it's attributed

The daily Cost Explorer total is unattributed. A rule can match the vendor, or a person can assign the row. Nothing on that pull names a profile or a tag.

On a FOCUS row, Meridian reads tags in this order. A cost-center tag whose value matches a department code or name sets the department. A saved tag mapping can pin a value to a department instead. There is no screen for that pin. Tagging says what the default keys are and how a saved mapping changes them. The row is inherited from the tag. An Agent tag sets the agent only when the value matches an existing agent name. A cost-center match is enough for a department even when the agent name does not match. If there is no tag match, the optional account crosswalk can still set a department.

A rule does not replace a department inherited from a tag. A person's assignment does not replace it either.

A FOCUS correction for an earlier period keeps that original period. If the month is locked, the correction becomes an adjustment line on a later draft.

What lands unattributed, and how to fix it

The Cost Explorer daily total lands unattributed. Fix it with a rule or an assignment, or stop using it as the attributed source and upload FOCUS instead. You cannot recover tags from the daily total. Cost Explorer was not asked for them.

FOCUS rows land in the inbox with one of these reasons:

• "Invoked by model ID, no inference profile." Call the model through an application inference profile and tag that profile.
• "No cost allocation tags." Activate the keys in AWS Billing, then upload a file that contains them. Tags can take up to 24 hours to become activatable and up to 24 hours to activate. (Bedrock cost best practices)
• "Agent or other tags present, but no cost center tag." Add a CostCenter, Department, or cost-center tag.
• "Cost center value not mapped." Add a department whose code or name matches the value, or pin the value with Onaro. There is no settings screen for that pin. See tagging.

An Agent tag with no matching agent name does not, by itself, send the row to the inbox when the cost center matched a department. The department is set. The agent is left empty. Create the agent with that name and upload again for new rows. Rows already inherited are not rewritten.

Limits

• The daily pull has no per-agent split. Three profiles on one account are one number per day.
• Request metadata on the invoke call is stored on the invocation log. It is not a Cost Explorer group, and the cost and usage report has no per-request line. (Request metadata)
• Cost from before the tag existed on the resource is empty. Backfill does not fill those months. Deactivating a key and then backfilling removes the key from prior months as well.
• A payer account can have 500 active user-defined cost-allocation tag keys. (Billing quotas)
• The agent tag does not create agents. The profile ARN is not the agent.
• Provisioned throughput and batch usage that lack a profile show the model-id reason when they are unattributed. They are not a separate split.
• Held Bedrock FOCUS rows are not imported while Cost Explorer is connected. Pick one source of record for those lines.