← Back to all announcements
★★☆☆☆ 11/05/2026

Announcing Region Expansion of P4de instances on SageMaker Studio notebooks

P4de's 640GB GPU memory and 60% faster training now reach Tokyo, Singapore, and Frankfurt—at 20% lower cost than P4d.

View original announcement →

Visual Summary

graph TD A{{P4de on SageMaker Studio}}:::announced B(SageMaker Studio):::compute C(NVIDIA A100 GPUs):::compute D([640GB HBM2e Memory]):::feature E([60% Better Training]):::feature F([Regional Expansion]):::feature G((Data Scientists)):::external H(JupyterLab / CodeEditor):::compute I([Large Model Training]):::feature G ==>|"launches"| B B ==>|"provisions"| A A -->|"powered by 8x"| C C -->|"provides"| D A -->|"enables"| E A -->|"Tokyo, Singapore, Frankfurt"| F B -->|"accessed via"| H D -->|"supports"| I classDef announced fill:#ff9900,stroke:#ec7211,color:#fff,font-weight:bold classDef compute fill:#e3f2fd,stroke:#1565c0,color:#1565c0 classDef storage fill:#e8f5e9,stroke:#2e7d32,color:#2e7d32 classDef feature fill:#fff3e0,stroke:#e65100,color:#e65100 classDef external fill:#f5f5f5,stroke:#616161,color:#616161

What's New

Amazon Web Services has expanded the availability of Amazon EC2 P4de instances on SageMaker Studio notebooks to three new regions: Asia Pacific (Tokyo), Asia Pacific (Singapore), and Europe (Frankfurt). These instances are equipped with 8 NVIDIA A100 GPUs, each featuring 80GB of HBM2e GPU memory, delivering a total of 640GB of GPU memory per instance. This expansion brings high-performance ML training capabilities closer to customers in Asia and Europe, enabling faster iteration and reduced latency for data-intensive workloads.

How It Works

  • P4de instances are powered by 8 NVIDIA A100 Tensor Core GPUs, each with 80GB of HBM2e high-bandwidth memory, totaling 640GB of GPU memory per instance.
  • HBM2e memory provides significantly higher memory bandwidth compared to previous generations, enabling faster data movement between GPU cores and memory during training operations.
  • The instances integrate directly with SageMaker Studio notebooks, accessible via JupyterLab and CodeEditor applications, allowing data scientists to launch GPU-backed notebook kernels without managing underlying infrastructure.
  • Users can configure and access P4de instances through the SageMaker Studio developer guides for both JupyterLab and CodeEditor environments, following standard instance selection workflows.
  • The instances leverage NVLink and high-speed interconnects between GPUs to support large-scale distributed training jobs that require tight GPU-to-GPU communication.

Why It's Important

  • The regional expansion reduces data residency and latency concerns for customers in Japan, Singapore, and Germany who must keep training workloads within specific geographic boundaries for compliance or regulatory reasons.
  • Up to 60% better ML training performance compared to P4d instances means teams can iterate on model development significantly faster, compressing experiment cycles and accelerating time to market.
  • A 20% lower cost to train relative to P4d instances means organizations get more compute value per dollar, making large-scale training more economically viable.
  • The 640GB total GPU memory pool enables training of very large models or processing of high-resolution datasets that would otherwise require complex model parallelism workarounds or be infeasible on lower-memory instances.
  • Availability within SageMaker Studio notebooks lowers the barrier to accessing this hardware tier, allowing data scientists to use it interactively without needing to configure standalone EC2 clusters.

How It's Different

  • P4de instances offer 2X the per-GPU memory (80GB vs. 40GB) compared to P4d instances, directly enabling larger batch sizes, bigger model checkpoints, and higher-resolution input data without out-of-memory errors.
  • The 60% ML training performance improvement over P4d translates to measurably shorter wall-clock training times for equivalent workloads, not just marginal gains.
  • Despite the significantly higher memory and performance, P4de instances cost 20% less to train on than P4d, inverting the typical trade-off between capability and cost.
  • HBM2e memory technology provides higher memory bandwidth than the HBM2 used in P4d instances, reducing memory bottlenecks in bandwidth-bound training scenarios such as large transformer models.
  • Integration with SageMaker Studio differentiates this from raw EC2 access by providing managed notebook environments, experiment tracking, and seamless access to other SageMaker features alongside the high-performance hardware.

When to Prefer It

  • Choose P4de when training large language models (LLMs) or foundation models that require more than 40GB of GPU memory per device and would otherwise require aggressive model sharding on P4d instances.
  • Prefer P4de for computer vision workloads involving high-resolution imagery (e.g., medical imaging, satellite imagery) where large input tensors quickly exhaust lower-memory GPUs.
  • Use P4de when operating in Asia Pacific (Tokyo), Asia Pacific (Singapore), or Europe (Frankfurt) and data sovereignty or latency requirements prevent routing workloads to other regions where P4de was previously available.
  • Select P4de over P4d when training cost efficiency is a priority, as the 20% lower training cost combined with faster completion times yields better overall economics for long-running jobs.
  • Opt for P4de in SageMaker Studio notebooks when data scientists need interactive, exploratory access to high-end GPU hardware without the overhead of provisioning and managing dedicated training clusters.
  • Consider P4de for multi-GPU distributed training experiments where the higher per-GPU memory reduces the need for gradient checkpointing or other memory-saving techniques that can slow training.

Availability

  • Status: Generally Available (GA) as of May 11, 2026.
  • New Regions: Asia Pacific (Tokyo), Asia Pacific (Singapore), and Europe (Frankfurt).
  • Access Method: Available through SageMaker Studio notebooks via JupyterLab and CodeEditor applications.
  • Pricing: Region-specific pricing is available on the AWS SageMaker pricing page; the instances offer approximately 20% lower cost to train compared to P4d instances.
  • Hardware Spec: Each P4de instance includes 8 × NVIDIA A100 GPUs with 80GB HBM2e memory each (640GB total GPU memory).
  • Prerequisite: Users should refer to the SageMaker Studio developer guides for setup instructions specific to JupyterLab and CodeEditor environments.

Tags

Servicessagemaker
Typeregion-expansionga-launch
Conceptstrainingmlops
Use Casesmulti-region
Providersnvidia
GeographyAPJEMEA

AI Radar AWS

AWS AI/ML news — curated, researched, explained

An automated intelligence platform that curates, researches, and analyzes AWS AI/ML/GenAI announcements daily. Every report is backed by real research — the system reads linked blog posts and documentation to provide accurate, in-depth analysis.

How Each Report Is Generated

  1. Collection — Daily monitoring of the AWS "What's New" RSS feed
  2. Filtering — AI-powered relevance detection for AI/ML/GenAI topics
  3. Taxonomy Tagging — LLM-based classification across 6 dimensions
  4. Importance Scoring — Point-based system with tag bonuses (1-5 stars)
  5. Research Phase — Follows links to blog posts and documentation
  6. Report Generation — Claude Sonnet produces structured 6-section analysis
  7. Visual Summary — Claude Opus generates Mermaid diagrams for key items
  8. Publishing — Static website rebuilt and deployed via CloudFront

Features

  • Faceted filtering by service, type, concept, and more
  • Multi-dimensional taxonomy with 80+ tags across 6 dimensions
  • Geographic availability badges (Global, APJ, EMEA, AMER) with filtering
  • Timeline visualization of announcement volume
  • PDF export for offline reading
  • Mermaid visual summaries for key announcements
  • Daily automated updates — no manual curation
What makes this different: Each report involves a dedicated research phase where the system reads linked blog posts and AWS documentation pages. This produces analysis that goes beyond the original announcement text.

Technology

Built with Python, AWS Lambda, Amazon Bedrock (Claude Sonnet 4.6, Opus 4.6, Haiku 4.5), S3, CloudFront, WAF, EventBridge, and CDK.

Open Source

This project is open source. Fork it, customize it for your needs, and deploy your own instance.
📦 github.com/bbonik/ai-radar-aws

How Importance Scoring Works

Each announcement receives a point score based on multiple factors. The total score maps to a 1-5 star rating:

1★ < 2 pts 2★ ≥ 2 pts 3★ ≥ 3.5 pts 4★ ≥ 5 pts 5★ ≥ 6.5 pts

Point Breakdown

FactorPointsWhen
Core AI service (Bedrock, AgentCore, SageMaker AI)+4Service named in title
Key AI service (SageMaker, Kiro, QuickSight)+2Service named in title
Other AI-related service+1Default
Blog post link+3Link to aws.amazon.com/blogs/
GitHub samples link+2Link to github.com/aws*
Documentation link+1Link to docs.aws.amazon.com/
New model+1.5Tagged as "new-model"
New service+1Tagged as "new-service"
New feature+0.5Tagged as "new-feature"
Anthropic / OpenAI provider+2Provider explicitly mentioned
Instance / notebook announcement-2Hardware/capacity, not feature
Performance / pricing / security-0.5Incremental updates
Region expansion to APJ+1Expands to Asia Pacific
Region expansion (non-APJ only)-1.5Only expands to other regions

Geographic Relevance Badges

Each announcement card shows a small badge indicating whether the feature is available in your region:

🌐 Global Available in all regions
🌏 APJ Asia Pacific
🌍 EMEA Europe / Middle East / Africa
🌎 AMER Americas (US, Canada, South America)
No badge Geography unknown
How geography is detected: The system detects ALL geographies mentioned in each announcement. If the text mentions specific regions (Tokyo, Frankfurt, Oregon, etc.), the corresponding geography badges are shown. If it says "all regions" or is a new feature with no region specified, it gets the Global badge. Geography is also filterable — click a geo chip to see only announcements available in that region.