Amazon Bedrock Integration

Overview

Grafient tracks your Amazon Bedrock spending by querying the AWS Cost Explorer API. This captures costs for all Bedrock models - Claude, Llama, Titan, Mistral, and any other model available through Bedrock - broken down by model and token direction (input/output).

Unlike providers with dedicated billing APIs, AWS uses its centralized Cost Explorer service for all cost data. Grafient queries this API daily to pull your Bedrock-specific costs.

Prerequisites

• An AWS account with Amazon Bedrock usage.
• Cost Explorer enabled on your AWS account (see Step 1 below).
• IAM permissions to create users and attach policies.
• A Grafient account on the Free, Pro, or Ultimate plan.

Step 1: Enable Cost Explorer

Cost Explorer must be activated before the API can be used. If you've already used Cost Explorer in the AWS Console, it's likely enabled.

1. Go to the AWS Cost Explorer Console.
2. If prompted, click Enable Cost Explorer.
3. Wait up to 24 hours for data to become available. AWS needs time to process your billing data after activation.

Step 2: Create an IAM User

1. Go to the AWS IAM Console.
2. Click Users in the sidebar, then Create user.
3. Enter a name (e.g. grafient-reader).
4. Click Next.
5. Select Attach policies directly.
6. Search for and attach the following AWS managed policy:
   • AWSBillingReadOnlyAccess - read-only access to Cost Explorer and billing data
7. Click Next, then Create user.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "ce:GetCostAndUsage",
      "Resource": "*"
    }
  ]
}

Step 3: Generate Access Keys

1. In the IAM Console, click the user you just created.
2. Go to the Security credentials tab.
3. Under Access keys, click Create access key.
4. Select Third-party service as the use case.
5. Check the confirmation box and click Next.
6. Click Create access key.
7. Copy both values - the Access Key ID and Secret Access Key. The secret is only shown once.

Step 4: Add the Integration in Grafient

1. In Grafient, navigate to Integrations in the sidebar.
2. Click Add Integration.
3. Select Amazon Bedrock as the provider.
4. Enter the Access Key ID from Step 3.
5. Enter the Secret Access Key from Step 3.
6. Optionally add a label (e.g. Production - AWS Bedrock).
7. Click Add Integration to save.

What Happens Next

Once connected, Grafient will:

1. Validate your credentials by making a test query to the Cost Explorer API.
2. Backfill historical costs - up to 30 days on Free, or 365 days on Pro/Ultimate (AWS Cost Explorer retains 12 months of data).
3. Sync daily - an automated sync pulls the latest Bedrock costs.

Costs appear on the Dashboard grouped by model (e.g. Claude 3 Sonnet, Llama 3 70B).

Data Collected

Data Freshness

AWS Cost Explorer data has a 12–24 hour delay. Cost data from today will typically appear tomorrow. This is an AWS limitation - the billing pipeline does not process in real time.

The daily sync captures the latest available data. For the most current view, click Force Sync on your integration card.

Troubleshooting

No cost data after sync

• Check for Bedrock usage: If there has been no Bedrock API usage, there will be no cost data. Verify in the AWS Console under Bedrock > Model access.
• Cost Explorer not enabled: Make sure you've completed Step 1. The API won't work until Cost Explorer is activated, even with the correct IAM permissions.
• Cost Explorer activation delay: If you just activated Cost Explorer, data may take up to 24 hours to appear.
• Try Force Sync: Click the refresh icon on your integration card to trigger a manual sync.

Cost data looks incomplete

• Bedrock only: Only Amazon Bedrock costs are tracked. Other AWS services (EC2, S3, etc.) are excluded.
• Data delay: Due to the 12–24 hour processing delay, yesterday's costs may not have arrived yet.
• On-Demand vs Provisioned: Both on-demand and provisioned throughput costs are captured if they appear under the Amazon Bedrock service in Cost Explorer.