Introducing OpenAI models on Amazon Bedrock for in-country inferencing in India
Amazon Bedrock now supports OpenAI GPT-5.6 models (Terra and Luna) for in-country inference in India, with data processing confined to Mumbai (ap-south-1) and Hyderabad (ap-south-2) regions Both models feature a 1-million-token context window, accept text and image input, and produce text output, enabling long document and mixed-workload processing India geographic cross-Region inference profiles (prefixed `in.`) automatically route requests within India for capacity scaling while maintaining da
Analysis
TL;DR
- Amazon Bedrock now supports OpenAI GPT-5.6 models (Terra and Luna) for in-country inference in India, with data processing confined to Mumbai (ap-south-1) and Hyderabad (ap-south-2) regions
- Both models feature a 1-million-token context window, accept text and image input, and produce text output, enabling long document and mixed-workload processing
- India geographic cross-Region inference profiles (prefixed
in.) automatically route requests within India for capacity scaling while maintaining data residency compliance - Global cross-Region inference profiles (prefixed
global.) are also available for maximum capacity, routing to commercial AWS Regions worldwide - Amazon Bedrock uses a zero data retention (ZDR) security model by default, with abuse-flagged content retained for offline detection
Why It Matters
This announcement is significant for AI practitioners and enterprises operating in India, as it addresses a critical pain point: data residency compliance when using leading commercial AI models. Organizations in regulated sectors like financial services, healthcare, and public sector can now leverage OpenAI's GPT-5.6 models without violating local data processing requirements. It also demonstrates AWS's strategy of bridging OpenAI's model capabilities with regional infrastructure to serve geographically constrained workloads.
Technical Details
- Models: OpenAI GPT-5.6 Terra and Luna, each with a 1-million-token context window, multimodal text/image input, and text-only output
- Inference Profiles: Two India-specific profile IDs —
in.openai.gpt-5.6-terraandin.openai.gpt-5.6-luna— route requests only between ap-south-1 and ap-south-2; global profiles use theglobal.prefix - API Support: Compatible with Amazon Bedrock's native Converse API, OpenAI Responses API, OpenAI Chat Completions API, and Anthropic Messages API via the
bedrock-runtimeendpoint - Security Model: Zero data retention (ZDR) by default; inputs/outputs are not stored, except content flagged by automated abuse-detection classifiers which is retained for offline review
- Monitoring & Billing: Billing, quota consumption, CloudWatch metrics, and CloudTrail logs are all tracked in the source Region regardless of which backend Region handles the request
- Authentication: Supports standard AWS credentials and Amazon Bedrock API keys (short-term keys programmatically generated via AWS SDK)
Industry Insight
- Data residency is becoming a competitive differentiator: AWS's move to offer in-country inference for OpenAI models signals that global AI providers must localize infrastructure to serve regulated markets — expect similar announcements in the EU, China, and other regions with strict data sovereignty laws.
- Cross-Region inference profiles simplify capacity management: The abstraction of routing requests across regions behind a single profile ID reduces operational complexity for enterprises scaling AI workloads, making it easier to maintain consistent throughput during traffic peaks without manual capacity planning.
- Enterprises should evaluate India vs. global profiles based on compliance needs: Workloads with strict data residency requirements should use
in.profiles, while non-sensitive, high-throughput applications may benefit fromglobal.profiles for maximum capacity — a strategic tradeoff between compliance and performance that architects must weigh per workload.
Disclaimer: The above content is generated by AI and is for reference only.