Latest in AI
Amazon Bedrock Web Search: Test Country Bias Separately From Language
Use country-aware Web Search in Bedrock Responses and verify that citations apply to the market being asked about.
A support assistant can answer in French and still cite the wrong country. If someone asks whether an appliance model is available in Belgium, a French page for shoppers in France might sound like the right source until you look at the market it serves.
AWS expanded Web Search on November 21, adding Spanish, French, German, Italian and Japanese, as well as non-US English. AWS also announced an optional country signal that favors sources from a chosen country. Existing users get the language expansion without a code change. Adding a country hint is a separate decision, and it doesn't remove the need to check citations.
Pass the target country explicitly
For the Bedrock Responses interface, the Web Search user guide places the country under the tool's user_location. Use an assigned ISO 3166-1 alpha-2 code, such as BE for Belgium or FR for France. AWS documents that an empty or missing location defaults to the United States. The tool also rejects unassigned codes such as UK; use GB for the United Kingdom.
A request's tools array can include this configuration:
[
{
"type": "web_search",
"external_web_access": false,
"user_location": {
"type": "approximate",
"country": "BE"
}
}
]
Treat this as a tool configuration fragment, not a complete request. The example keeps external page retrieval disabled. Preserve your application's approved retrieval policy when adding location, so a country test doesn't accidentally change how pages are fetched. AWS announced the expansion for AgentCore too, but this example is for Bedrock Responses, not a payload for the AgentCore Gateway or direct search API.
Choose the country from the question or an explicit market setting. Don't infer it from language alone. A user in Belgium could ask about a model they want to buy in France, and the French answer can be right in either case. If the question materially depends on the market and you can't tell which one they mean, ask.
Change one retrieval variable at a time
For a product-support pilot, choose several appliance models with country-specific product pages. Keep a small set of expected evidence: the model identifier, the correct market page and the claim it supports. Avoid making live stock a pass condition unless the source actually reports stock.
Send the same French question three ways: with no location, with BE, and with FR. Keep the model, prompt, requested answer language and retrieval policy fixed. The unconfigured request is a useful control, not a locale-neutral baseline, because Bedrock documents a US default.
Next, repeat the Belgium case in English without changing the country. That gives you a separate check: does changing the language of the question send the assistant back to sources for a different market?
Grade sources before grading answers
Open the citations and check what they prove. A Belgian URL alone doesn't confirm that it describes the right model, and a global manufacturer's page may verify specifications without establishing local availability. Mark those separately rather than giving credit whenever an answer sounds plausible.
For each case record the requested and configured country, cited page, market named by the page and whether the source supports the claim. Flag a wrong-market citation even if a reviewer believes the conclusion happens to be correct.
Country is a preference, not a hard source boundary. If your application needs to restrict results to known domains for a particular task, Bedrock documents a separate domain filtering option. Even then, inspect the source for market scope; a domain may serve multiple countries.
Keep deployment Region out of the locale decision
AWS says Web Search queries are processed in the Region called. The country you pass is for localization, not infrastructure placement. Verify the endpoint and processing requirements separately before rollout.
Start with a few clearly labeled markets, then expand when the citation checks pass. If the system finds a product but cannot verify the requested market, say that plainly. A useful country hint improves the search; it should not give the assistant permission to fill in the gaps.
I'm Paras. I work at the intersection of AI, engineering and distribution.
I help AI teams explain technical products through clear documentation, practical guides and developer-focused content.