---
title: OpenAI GPT-5.6 Luna & Terra Price Cuts on Amazon Bedrock (July 2026)
description: On July 30, 2026 AWS cut Bedrock on-demand prices 80% for GPT-5.6 Luna and 20% for Terra — Luna is now $0.22/$1.32 per 1M tokens. Here is the routing math and what not to re-price overnight.
url: https://www.factualminds.com/blog/openai-gpt-5-6-luna-terra-bedrock-pricing-2026/
datePublished: 2026-07-31T00:00:00.000Z
dateModified: 2026-07-31T00:00:00.000Z
author: palaniappan-p
category: Generative AI
tags: bedrock, openai, cost-optimization, genai, finops, foundation-models
---

# OpenAI GPT-5.6 Luna & Terra Price Cuts on Amazon Bedrock (July 2026)

> On July 30, 2026 AWS cut Bedrock on-demand prices 80% for GPT-5.6 Luna and 20% for Terra — Luna is now $0.22/$1.32 per 1M tokens. Here is the routing math and what not to re-price overnight.

> **AWS lifecycle notice (June 30, 2026)** — Amazon Bedrock Agents Classic is in maintenance for new customers after **July 30, 2026**. Net-new agent builds should use [Bedrock AgentCore](/blog/amazon-bedrock-agentcore-production/). Full matrix: [lifecycle roundup](/blog/aws-service-lifecycle-updates-june-2026/).

On **July 30, 2026**, AWS [announced](https://aws.amazon.com/about-aws/whats-new/2026/07/openai-gpt-terra-luna-pricing-bedrock/) that on-demand inference prices on Amazon Bedrock for **OpenAI GPT-5.6 Luna** dropped **80%** and **GPT-5.6 Terra** dropped **20%**, in line with [OpenAI’s first-party price cut](https://openai.com/index/advancing-the-price-performance-frontier-with-gpt-5-6/). **GPT-5.6 Sol is unchanged.** The new rates apply automatically.

This is a **routing and FinOps event**, not a “flip the default model ID” event. If you already run OpenAI on Bedrock (see our [April 2026 OpenAI-on-Bedrock analysis](/blog/amazon-bedrock-openai-models-codex-managed-agents/)), recalculate cost per completed task by lane — then promote only the lanes that still pass quality.

---

## What changed on the Bedrock rate card

Published **Amazon Bedrock** on-demand rates after the cut (US East N. Virginia / Ohio and US West Oregon where listed):

| Model             | Input / 1M tokens | Output / 1M tokens | Cache read / 1M | Cut vs prior |
| ----------------- | ----------------: | -----------------: | --------------: | ------------ |
| **GPT-5.6 Luna**  |             $0.22 |              $1.32 |          $0.022 | **−80%**     |
| **GPT-5.6 Terra** |             $2.20 |             $13.20 |           $0.22 | **−20%**     |
| **GPT-5.6 Sol**   |             $5.50 |             $33.00 |           $0.55 | Unchanged    |

Source: [Amazon Bedrock pricing](https://aws.amazon.com/bedrock/pricing/) (OpenAI frontier table, post–July 30, 2026). OpenAI’s global API list is slightly lower ($0.20/$1.20 Luna; $2/$12 Terra); Bedrock’s published in-region figures track OpenAI’s **data-residency** tier (~10% uplift). Treat the Bedrock page as the budget source of truth for AWS bills.

Implied prior Bedrock-equivalent rates (from the stated 80% / 20% cuts): Luna ≈ **$1.10 / $6.60**, Terra ≈ **$2.75 / $16.50** per 1M input/output.

AWS positions the tiers the same way it did at [GPT-5.6 GA](https://aws.amazon.com/blogs/machine-learning/openai-gpt-5-6-sol-terra-and-luna-are-now-generally-available-on-amazon-bedrock/):

- **Luna** — fast, high-volume: classification, summarization, routing, customer-service automation, routine tool workflows
- **Terra** — everyday production with stronger reasoning at GPT-5.5-class quality, lower cost
- **Sol** — flagship multi-step / agentic reasoning (price unchanged — do not expect this cut to move Sol TCO)

---

## First-party pricing math (not a client silhouette)

No anonymized engagement is cited for this specific July 30 cut. The numbers below are **reproducible arithmetic on the published Bedrock rate card** — one illustrative monthly shape, labeled as math.

**Illustrative Luna month:** 50M input tokens + 5M output tokens (high-volume classification / routing mix).

| Period               |               Input |             Output | Monthly total |
| -------------------- | ------------------: | -----------------: | ------------: |
| Pre-cut (implied)    | 50 × $1.10 = $55.00 | 5 × $6.60 = $33.00 |    **$88.00** |
| Post-cut (published) | 50 × $0.22 = $11.00 |  5 × $1.32 = $6.60 |    **$17.60** |

**Direction:** −$70.40 / month (−80%) for that token mix on Luna alone. Same volume on Terra post-cut: (50 × $2.20) + (5 × $13.20) = **$176.00** — still ~10× Luna for identical token counts, which is why model choice still dominates the bill.

> **Reproduce this** — Open the [Bedrock pricing](https://aws.amazon.com/bedrock/pricing/) OpenAI table. Multiply your Cost Explorer / CUR input and output token totals by the Luna and Terra rows. For cache-heavy agent loops, include cache-write and cache-read lines separately (90% discount on cache read). If totals diverge, you are missing a service tier or Mantle usage type — see AWS’s [CUR Bedrock token-type guide](https://docs.aws.amazon.com/bedrock/latest/userguide/cost-mgmt-understanding-cur-data.html).

Pair this with the broader playbook in [Bedrock cost optimization: token budgets and model selection](/blog/aws-bedrock-cost-optimization-token-budgets-model-selection/).

---

## Opinionated routing after the cut

**We recommend:** default **new** high-QPS classification / extraction / thin-tool lanes to **Luna** on Bedrock Mantle **after** a frozen-prompt quality bakeoff. Keep everyday agentic production on **Terra** until Luna’s pass rate matches. Keep deep overnight / exploit-class / multi-hundred-step agents on **Sol** (or Claude Opus 5 where ZDR-default + Guardrails composition matter more — see [Opus 5 on Bedrock](/blog/claude-opus-5-aws-bedrock-2026/)).

**Trade-off you accept:** lower $ / MTok on Luna vs higher risk of silent quality regressions on nuanced prompts if you promote by price alone.

| Lane                                                      | Prefer after July 30                     | Why                                                                                                                |
| --------------------------------------------------------- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| Classification, routing, summarization, high-QPS chat     | **Luna**                                 | −80% list price; built for volume                                                                                  |
| Everyday code gen, structured extraction, mid-tier agents | **Terra** (−20%)                         | Stronger reasoning without Sol rates                                                                               |
| Long-horizon agents, cyber research, hardest coding       | **Sol** (unchanged) or **Claude Opus 5** | Capability / governance, not this price event                                                                      |
| Cheap AWS-native alternatives                             | **Nova** / Haiku                         | Still worth A/B when OpenAI-specific behavior is not required — [Nova guide](/blog/aws-bedrock-nova-models-guide/) |

For the enterprise Bedrock-vs-direct-API frame (IAM, PrivateLink, commitments), see [AWS Bedrock vs OpenAI API](/blog/aws-bedrock-vs-openai-api-enterprise/).

---

## What broke (pattern): “cheaper tokens, same task cost”)

> **What broke** — Teams that only reprice the model ID and leave prompts, `max_output` / completion budgets, and tool-loop depth unchanged often see **token $ drop while cost per completed task barely moves**. Root cause: Luna (and Terra) still bill output heavily relative to input; verbose system prompts and uncapped completions dominate. Detect via CUR: output-token $ share stays >50% of the model line. Fix: cap max output per lane, add prompt-cache breakpoints for sticky prefixes (90% cache-read discount), and measure **$ / successful task**, not $ / 1K tokens.

On-demand still wins for spiky traffic; if you were about to buy Provisioned Throughput for a Luna-class lane, re-run the break-even after this cut — [on-demand vs Provisioned Throughput](/blog/aws-bedrock-provisioned-throughput-vs-on-demand-break-even-2026/).

---

## Invoke Luna / Terra on Mantle (Responses API)

Context: OpenAI Python SDK against Bedrock Mantle, region `us-east-1`, model IDs from the [Luna](https://docs.aws.amazon.com/bedrock/latest/userguide/model-card-openai-gpt-56-luna.html) / [Terra](https://docs.aws.amazon.com/bedrock/latest/userguide/model-card-openai-gpt-56-terra.html) model cards. Auth via Bedrock API key or SigV4 as documented for your path.

```python
# openai>=1.x; OPENAI_BASE_URL=https://bedrock-mantle.us-east-1.api.aws/openai/v1
from openai import OpenAI

client = OpenAI()  # uses OPENAI_API_KEY + OPENAI_BASE_URL from env

response = client.responses.create(
    model='openai.gpt-5.6-luna',
    input='Classify this support ticket into billing, outage, or how-to. Reply with one label only.',
)

print(response)
```

Swap `openai.gpt-5.6-terra` for mid-tier lanes. Regions today: `us-east-1`, `us-east-2`, `us-west-2` for Luna/Terra; Sol is `us-east-1` / `us-east-2` only. Geo/global inference IDs are **not supported** on these Mantle model cards at time of writing — plan capacity inside those Regions.

---

## What to Do This Week

1. Pull last 30 days of Bedrock OpenAI token usage from Cost Explorer / CUR; split by model ID.
2. Recompute monthly $ at the new Luna / Terra rows; leave Sol at $5.50 / $33.
3. Pick **one** high-volume lane that is not Sol-dependent; freeze 50–100 production prompts; score Luna vs current model on pass rate, p95 latency, and **$ / completed task**.
4. Enable prompt caching on sticky system + tool prefixes; confirm cache-read lines appear in CUR.
5. Update budgets and anomaly detectors — an 80% Luna drop can look like a “usage cliff” to naive alerts ([FinOps Agent / Cost Anomaly context](/blog/aws-finops-agent-preview-bedrock-cost-anomaly-2026/)).
6. If you are still on OpenAI direct for regulated data, revisit Bedrock for commitment consolidation and IAM — [GenAI on AWS](/services/generative-ai-on-aws/) / [Amazon Bedrock consulting](/services/aws-bedrock/).

---

## What This Post Doesn't Cover

- A published FactualMinds latency/quality bakeoff of Luna vs Terra vs Claude Haiku/Sonnet on our prompt packs (no harness linked yet).
- OpenAI Fast-mode / Flex / Batch tier matrices beyond pointing at the OpenAI and Bedrock rate cards.
- Codex-on-Bedrock developer UX (covered in the [OpenAI models + Codex post](/blog/amazon-bedrock-openai-models-codex-managed-agents/)).
- EU / non-US regional availability for GPT-5.6 Sol/Terra/Luna beyond the three US Regions AWS listed.

Use the rate card + your CUR. Promote lane-by-lane.

---

## Related reading

- [Amazon Bedrock + OpenAI Models, Codex & Managed Agents](/blog/amazon-bedrock-openai-models-codex-managed-agents/)
- [AWS Bedrock vs OpenAI API: Enterprise Decision Guide](/blog/aws-bedrock-vs-openai-api-enterprise/)
- [AWS Bedrock Cost Optimization: Token Budgets and Model Selection](/blog/aws-bedrock-cost-optimization-token-budgets-model-selection/)
- [Bedrock Provisioned Throughput vs On-Demand Break-Even](/blog/aws-bedrock-provisioned-throughput-vs-on-demand-break-even-2026/)
- [Claude Opus 5 on AWS Bedrock (July 2026)](/blog/claude-opus-5-aws-bedrock-2026/)
- [Amazon Bedrock Nova Models Guide](/blog/aws-bedrock-nova-models-guide/)
- [Generative AI on AWS](/services/generative-ai-on-aws/) · [Amazon Bedrock services](/services/aws-bedrock/) · [AWS cost optimization](/services/aws-cloud-cost-optimization-services/)

## FAQ

### How much did GPT-5.6 Luna and Terra drop on Amazon Bedrock?
Effective July 30, 2026, AWS reduced on-demand inference prices for GPT-5.6 Luna by 80% and GPT-5.6 Terra by 20%, matching OpenAI first-party changes. Sol pricing is unchanged. New prices apply automatically — no code or console change is required for the rate cut itself.

### What are the current Bedrock on-demand rates for GPT-5.6 Luna and Terra?
As published on the Amazon Bedrock pricing page after the cut (US East / US West standard on-demand): Luna $0.22 per 1M input tokens and $1.32 per 1M output tokens; Terra $2.20 / $13.20; Sol $5.50 / $33.00. Cache-read input is billed at a 90% discount ($0.022 Luna, $0.22 Terra). Bedrock in-region rates sit ~10% above OpenAI global API list because they track OpenAI data-residency tier. Always re-check aws.amazon.com/bedrock/pricing/ before budgeting.

### Should we move every OpenAI lane to Luna after the 80% cut?
No. Luna is positioned for high-volume classification, summarization, routing, content processing, and routine tool workflows where latency and cost per token dominate. Terra remains the everyday production / stronger-reasoning tier. Sol stays the flagship for deep multi-step agentic work. Promote by lane using cost per completed task and quality pass rate — not token list price alone.

### When should we NOT switch models after this price cut?
Hold if (1) the lane already meets quality and latency SLAs on Claude Haiku/Sonnet, Nova, or Terra, (2) you have not re-measured quality on Luna with frozen production prompts, (3) output-token length or tool-loop depth makes Sol/Terra still cheaper per completed task, (4) your residency or Mantle endpoint constraints are unmet, or (5) prompt-cache breakpoints are sized for another model family and would thrash on Luna.

### Does GPT-5.6 usage on Bedrock count toward AWS commitments?
Yes. AWS states OpenAI model usage on Bedrock counts toward existing AWS commitments, and pricing matches OpenAI first-party rates (with Bedrock residency-tier differences as published). Spend consolidates on the AWS bill rather than a parallel OpenAI invoice.

### Which regions and API path do Luna and Terra use on Bedrock?
GPT-5.6 Luna and Terra are available in US East (N. Virginia), US East (Ohio), and US West (Oregon) via the OpenAI Responses API on the bedrock-mantle endpoint. Model IDs: openai.gpt-5.6-luna and openai.gpt-5.6-terra. Sol is available in us-east-1 and us-east-2. Confirm the live model cards before hardcoding region assumptions.

---

*Source: https://www.factualminds.com/blog/openai-gpt-5-6-luna-terra-bedrock-pricing-2026/*
