<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bedrock on Kuldeep Pisda</title><link>https://kdpisda.in/tag/bedrock/</link><description>Recent content in Bedrock on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 18 Aug 2026 09:00:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/bedrock/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS Bedrock Now Speaks OpenAI Natively, and Routes GPT-5.6 Across Regions</title><link>https://kdpisda.in/aws-bedrock-cross-region-openai-gpt-5-6/</link><pubDate>Tue, 18 Aug 2026 09:00:00 +0530</pubDate><guid>https://kdpisda.in/aws-bedrock-cross-region-openai-gpt-5-6/</guid><description>&lt;p&gt;AWS announced yesterday that Bedrock now runs OpenAI&amp;rsquo;s GPT-5.6 models, Sol, Terra, and Luna, directly on the &lt;code&gt;bedrock-runtime&lt;/code&gt; endpoint, speaking the Responses API, Chat Completions API, and Converse API natively. Alongside that, it shipped cross-Region inference for those models: Geo routing that keeps requests inside a defined geography, and Global routing that spreads them across every commercial Region where the model is available.&lt;/p&gt;
&lt;p&gt;This matters more than a typical &amp;ldquo;new model available&amp;rdquo; note. Since OpenAI models landed on Bedrock, they sat slightly apart from the rest of the platform: teams either translated their existing OpenAI SDK calls into Bedrock&amp;rsquo;s Converse format, or ran a parallel path outside Bedrock&amp;rsquo;s governance just to keep using the Responses API shape their code already expected. That workaround is now gone, and the routing decision it exposes, cost versus latency versus data residency, is one every team running GPT-5.6 at scale now has to make explicitly.&lt;/p&gt;</description></item></channel></rss>