Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Story

SageMaker AI launches cross-Region inference routing

AI summary

AWS Machine Learning Blog says Amazon SageMaker AI cross-Region inference routing is generally available as of November 18, 2026, in commercial Regions supporting real-time endpoint inference. Salesforce uses the feature to route requests across its existing endpoints in multiple Regions and accounts, adding serving capacity while preserving data residency commitments. The router does not create capacity or copy models, and operators can cap remote traffic to protect capacity reserved for local requests.

In-depth insight

The managed routing path gives Salesforce a capacity-aware alternative to application-level failover while providing explicit controls for cross-Region traffic and data residency.

Thanks to Amit Gupta, Senior Director- AI/ML and Mark Wang, Software Engineering PMTS from Salesforce for your contributions in the vision and partnership of cross-Region inference routing on SageMaker AI.

Salesforce’s Agentforce Foundation team serves a wide variety of models for products across Salesforce, including Agentforce and the Salesforce Trust Layer, in 30+ global Regions. These include both models trained in house and open source models. Hosting models separately in each Region splits capacity and makes traffic spikes harder to absorb, which turns a capacity shortfall into an availability problem.

This post shows how Salesforce set up the cross-Region inference routing in SageMaker AI and how it lets the team add capacity securely while keeping its data residency commitments. It also walks through how Salesforce sees where each request was served and why. The cross-Region inference routing gives an application one invocation path across SageMaker AI endpoints in several Regions and accounts, and sends each request to an endpoint that can serve it. Those endpoints are Salesforce’s own, already deployed. The post starts with the capacity problem Salesforce faced, explains how the router works and how Salesforce integrated it into its Internal Gateway, walks through an example setup, and then describes what the team observed.

#Amazon SageMaker AI#AWS#Salesforce#Agentforce#Salesforce Trust Layer

Original · 13 min readRead the original
Group chat

No comments yet. Start the conversation.