AIToday
Large Language ModelsAI Business & IndustryAmazon AI BlogPublished: Aug 29, 2026, 04:00 JST

Salesforce meets Multi-AZ HA with new SageMaker IC placement

Salesforce meets Multi-AZ HA with new SageMaker IC placement

3 Key Points

  1. What happened

    Salesforce used the new IC Placement capability in Amazon SageMaker AI Inference Components to make its Agentforce models highly available across multiple Availability Zones. The new SchedulingConfig parameter controls copy placement across instances and AZs.

  2. Why it matters

    The ICs cut infrastructure costs by 8x by co-hosting models on shared GPUs, but default placement didn't meet Salesforce's compliance bar of 2-AZ support for every production model. The new placement algorithm balances copies across AZs and instances to avoid single points of failure.

  3. What to watch

    AWS recommends setting CopyCount to at least 2 and using SPREAD placement with MaxImbalance 0 or 1 to maintain 2-AZ compliance. Salesforce chose SPREAD to prioritize fault isolation over packing density.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

Salesforce's challenge was that while SageMaker Inference Components cut GPU costs by sharing hardware, the default placement algorithm didn't consider AZ balance, risking single points of failure. The new SchedulingConfig parameter addresses this by letting customers control placement with AvailabilityZoneBalance and PlacementStrategy. Salesforce chose SPREAD to maximize fault isolation, ensuring a single instance failure doesn't take down multiple copies of a model. The feature also supports scaling while maintaining balance, and AWS recommends using On-Demand Capacity Reservations for capacity planning in high-demand regions. Monitoring tools like SageMaker AI Insights help track AZ balance and rebalancing events to maintain compliance over time.

FAQ
What is the new SchedulingConfig parameter?
It's a parameter in the CreateInferenceComponent API that gives customers fine-grained control over where AI model copies are placed across instances and Availability Zones.
Why did Salesforce need this feature?
Default placement didn't guarantee Multi-AZ resilience, and Salesforce mandates 2-AZ support for every production model to meet compliance requirements.
Amazon AI BlogRead Original Article

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleNvidia beats expectations, eyes Hugging Face buy