What Happened
- October 23: Amazon Bedrock Web Search added domain filtering and optional user-location controls on the web_search tool in OpenAI Responses API requests. Teams can specify up to 100 allowed domains or 100 blocked domains. The controls are available where Bedrock Web Search is supported: US East (N. Virginia and Ohio), US West (Oregon), and AWS GovCloud (US-West). [1]
- October 23: Amazon Connect Customer Global Resiliency added persistent chat across linked AWS Regions. A customer can resume a conversation in another linked Region with its context, metadata, transcript, and attachments preserved. Use requires onboarding to Global routing. [2]
- October 22: Amazon announced quarterly security and critical updates for Corretto: 27.0.1.0.10, 25.0.5.0.9, 21.0.13.0.10, 17.0.21.0.10, 11.0.33.0.9, and 8u512. Downloads and Linux Apt, Yum, and Apk repositories are available. [3]
Why It Matters to Businesses
These changes address three different production concerns: which web sources an AI application can retrieve, whether a customer conversation survives a regional transition, and whether Java runtimes receive current fixes. Each is useful only if teams update the surrounding configuration, tests, and operating procedures. [1][2][3]
Kimbodo Engineering Perspective
Domain filtering can narrow a search surface, but it does not establish that an allowed page is accurate or safe to follow. Location improves relevance only when the application has an appropriate location value to pass. Cross-Region chat continuity is similarly more than a routing switch: teams need to verify how transcripts and attachments behave during failover. Corretto releases should follow normal compatibility testing rather than being treated as a version-number change alone. [1][2][3]
How We Would Implement It
- Put Bedrock Web Search settings in version-controlled tool configuration. Choose an allowlist or blocklist for each use case, pass location only when appropriate, and test returned domains and regional availability. [1]
- Onboard Amazon Connect to Global routing, then rehearse a chat handoff between linked Regions. Check conversation context, metadata, transcripts, attachments, and agent workflows after the transition. [2]
- Inventory Corretto versions across images and hosts, update through the applicable distribution channel, run application and dependency tests, and deploy progressively with a rollback path. [3]
Risks, Costs and Security
Review what location data the application sends to search and treat retrieved pages as untrusted input. For persistent chat, confirm that access controls, retention requirements, and regional data-handling policies cover transcripts and attachments in both linked Regions. Budget for failover testing and rollout work; do not assume these releases remove existing service or infrastructure costs. [1][2]
Where Kimbodo Comes In
Kimbodo builds and operates this in production for businesses — see our AI Application Development practice, or Estimate My AI Application.
