Amazon Bedrock now offers xAI’s Grok 4.7, giving AWS customers a new model option for coding, long-running agents and knowledge work. It supports a 500,000-token context window and four reasoning-effort settings, with practical choices around cost, speed and where requests are processed.
AWS AI Watch analysis
What happened
AWS announced the availability on 28 September. The model is served through Bedrock’s cross-Region inference profiles and supports the Responses, Chat Completions and Converse APIs, alongside InvokeModel. Developers can use the OpenAI SDK or AWS SDKs, depending on their integration.
Our top picks
- A 500,000-token context window
Grok 4.7 can take in long prompts and reference material for extended tasks. - Four reasoning-effort settings
Choose low, medium, high or xhigh; AWS says high is the default. - Three service tiers
Standard, Priority and Flex offer different trade-offs between price and processing priority. - Two inference profiles
The US profile keeps processing within the US geography; Global offers broader routing at a lower price, with less control over where requests are served. - Bedrock features remain in play
Prompt caching, Guardrails, structured outputs and invocation logging are available for supported workflows.
Why it matters
This is more than a model appearing in another catalogue: Bedrock users can choose their API route, service tier and inference profile, while keeping it within AWS’s tooling. Those choices matter for teams balancing latency, cost, data-residency needs and integration work.
AWS’s post attributes the capability and performance descriptions to xAI, and summarises evaluations from Artificial Analysis. Treat those results as reported comparisons, not a promise about every workload. One operational detail is worth noticing: reasoning is active, and effort settings affect cost and latency. Setting the level deliberately is wiser than letting a default pick the tab.
Our read
For teams already building on Bedrock, Grok 4.7 is a substantial new option, particularly where long-context or agent workflows are the point. Check the profile, service tier and reasoning effort against your requirements before moving production traffic; the model name is the easy part.
What to watch
- How Grok 4.7 performs on customer workloads compared with existing Bedrock models.
- Whether teams find the Global profile’s price advantage worth its looser regional control.
- How actual token use and latency vary across reasoning-effort settings.
Discussion spark: Would you choose the cheaper Global profile for a Bedrock workload, or pay more to keep processing within a specific geography?
Sources and evidence
- Grok 4.7 is now available on Amazon Bedrock (28 September 2026, 22:13 UTC)
not affiliated with or endorsed by Amazon Web Services (AWS)