Better tools. Better news.
Sunday, November 22, 2026 · UTC
AI

AWS Bedrock Web Search tool launches in GovCloud (US-West) for government workloads

AWS announced Web Search on Amazon Bedrock is now available in AWS GovCloud (US-West) for government workloads.

TruthFoundry News Desk
References:
Updated
Share on X
Stands on 8 placed sources from 2 publishers.
Amazon Web Services (AWS) announced that the Web Search built-in server-side tool on Amazon Bedrock is now available in AWS GovCloud (US-West), targeting compliance-sensitive government and public-sector workloads. [1] Researchers propose AutoXRD, an autonomous large language model agent framework that organizes powder X-ray diffraction analysis as stepwise refinement. [2] According to Amazon Web Services, Web Search grounds responses from supported OpenAI GPT models with information from the web and includes citations so users can trace each claim back to its web origin. [3] Amazon Web Services said the Web Search tool runs inside Amazon Bedrock, meaning customers do not need to host a search index, manage crawlers, or write the tool-call loop themselves. [4] Amazon Web Services stated that by default, Web Search keeps request data within the AWS boundary and is governed by AWS Identity and Access Management (IAM), allowing administrators to allow or deny it at the account or organization level and restrict it by Region. [5] Models averaged only 57.8 out of 100 points across 1,340 model-task runs, falling from 61.9 on XRDBench-QA to 53.7 on XRDBench-E2E. [6] Models performed best on refinement-history assessment and result acceptance but remained substantially weaker on refinement-action selection, phase quantification, indexing, and Rietveld refinement. [7] The AutoXRD framework grounds actions in observed evidence and applies deterministic crystallographic and physical checks before accepting results. [8]
Proof8 sources · 2 publishers
What this stands on
  1. Amazon Web Services (AWS) announced that the Web Search built-in server-side tool on Amazon Bedrock is now available in AWS GovCloud (US-West), targeting compliance-sensitive government and public-sector workloads. · Amazon Web Services, Inc.
  2. Researchers propose AutoXRD, an autonomous large language model agent framework that organizes powder X-ray diffraction analysis as stepwise refinement. · arXiv.org
  3. According to Amazon Web Services, Web Search grounds responses from supported OpenAI GPT models with information from the web and includes citations so users can trace each claim back to its web origin. · Amazon Web Services, Inc.
  4. Amazon Web Services said the Web Search tool runs inside Amazon Bedrock, meaning customers do not need to host a search index, manage crawlers, or write the tool-call loop themselves. · Amazon Web Services, Inc.
  5. Amazon Web Services stated that by default, Web Search keeps request data within the AWS boundary and is governed by AWS Identity and Access Management (IAM), allowing administrators to allow or deny it at the account or organization level and restrict it by Region. · Amazon Web Services, Inc.
  6. Models averaged only 57.8 out of 100 points across 1,340 model-task runs, falling from 61.9 on XRDBench-QA to 53.7 on XRDBench-E2E. · arXiv.org
  7. Models performed best on refinement-history assessment and result acceptance but remained substantially weaker on refinement-action selection, phase quantification, indexing, and Rietveld refinement. · arXiv.org
  8. The AutoXRD framework grounds actions in observed evidence and applies deterministic crystallographic and physical checks before accepting results. · arXiv.org
We do not know which country they publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
Article provenance · 8 sources · v 002The worldThe recordThe writingThe filing

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Wednesday, September 2, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events across 2 source articles
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
We do not know which country they publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
From another Newsroom Floor paper, with its byline. Each piece opens on the paper that wrote it.
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.
Integrity
Content hash (SHA-256)3fb62e2191cb00f5bd347a380b6ed0682383d2883c87ad9e531e263acfc49bb4
Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receiptthis revision predates receipt-keeping; the filed row lives on the record
Machine readablethe full proof, JSON
Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.