AWS AI Cost Optimization: SageMaker vs. Bedrock vs. EC2

Scenario

A delivery team needs a practical playbook that turns cost optimization from a one-time cleanup into a weekly engineering routine. This article focuses on AI workload economics, token controls, and production guardrails on AWS.

Why this matters

• Costs increase quietly when ownership is unclear.
• FinOps succeeds when engineering actions are automated.
• Small recurring reductions compound into major annual savings.

Reference architecture

Environment bootstrap commands

export AWS_REGION=us-east-1
export AWS_PROFILE=default
export REPORT_START=$(date -u -d "30 days ago" +%Y-%m-%d)
export REPORT_END=$(date -u +%Y-%m-%d)

$env:AWS_REGION = "us-east-1"
$env:AWS_PROFILE = "default"
$env:REPORT_START = (Get-Date).AddDays(-30).ToString("yyyy-MM-dd")
$env:REPORT_END = (Get-Date).ToString("yyyy-MM-dd")

Baseline inventory command set

aws ce get-cost-and-usage \
  --time-period Start=$REPORT_START,End=$REPORT_END \
  --granularity DAILY \
  --metrics UnblendedCost \
  --group-by Type=DIMENSION,Key=SERVICE

Launch script for weekly cost audit

Save this script as scripts/weekly-cost-audit.sh and run it from CI every Monday.

#!/usr/bin/env bash
set -euo pipefail
OUT=./finops
mkdir -p "$OUT"
aws ce get-cost-and-usage \
  --time-period Start="$REPORT_START",End="$REPORT_END" \
  --granularity DAILY \
  --metrics UnblendedCost \
  --group-by Type=DIMENSION,Key=SERVICE > "$OUT/cost-by-service.json"
aws ce get-rightsizing-recommendation \
  --service EC2-Instance \
  --region "$AWS_REGION" > "$OUT/ec2-rightsizing.json"

Validation runbook

1. Pull 30-day spend grouped by service.
2. Capture utilization metrics for top 5 cost drivers.
3. Create a backlog item for every optimization with owner and due date.
4. Re-run the audit after changes and compare deltas.

Cost scoreboard template

AI-specific optimization controls

1. Enforce per-request token caps and max output limits.
2. Add model routing rules: small model first, escalate only for hard prompts.
3. Cache deterministic prompts and retrieval context aggressively.
4. Batch non-urgent inference jobs into scheduled windows.
5. Trigger an automated kill switch when anomalies cross threshold.

Implementation timeline

1. Week 1: Baseline, tagging, and budget alerts.
2. Week 2: Rightsizing and idle resource cleanup.
3. Week 3: Commitment strategy and storage/network tuning.
4. Week 4: Automation, policy checks, and executive reporting.

Visual trend sample

Practical tips

• Keep one source of truth for savings assumptions and actual results.
• Never optimize production blindly; test in lower environments first.
• Review cost impact in every architecture proposal before implementation.

Final takeaway

Use this article as a launch-ready operating runbook. The fastest teams are not the teams that spend the most; they are the teams that measure, automate, and improve continuously.