2025-12-04_aws-trainium3-deep-dive-a-potential::TRN3-0006
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Amazon’s Software North Star - Line hint:
63
Context Before
Amazon’s Software North Star
On the software front, AWS’s North Star expands and opens their software stack to target the masses, moving beyond just optimizing perf per TCO for internal Bedrock workloads (ie DeepSeek/Qwen/etc which run a private fork of vLLM v1) and for Anthropic’s training and inference workloads (which runs a custom inference engine and all custom NKI kernels).
Evidence
Phase 1 is releasing and open sourcing a new native PyTorch backend.
Context After
By open sourcing most of their software stack, AWS will help broaden adoption and kick-start an open developer ecosystem. We believe the CUDA Moat isn’t constructed by the Nvidia engineers that built the castle, but by the millions of external developers that dig the moat around that castle by contributing to the CUDA ecosystem. AWS has internalized this and is pursuing the exact same strategy.
Trainium3 will only have Day 0 support for Logical NeuronCore (LNC) ↗ = 1 or LNC = 2. LNC = 1 or LNC = 2 is what ultra-advanced, elite L337 kernel engineers at Amazon/Anthropic want, but LNC=8 is what the wider ML research scientist community prefers before widely adopting Trainium. Unfortunately, AWS does not plan on supporting LNC=8 until mid-2026. We will expand much more on what LNC is and why the different modes are critical for research scientist adoption further down.
② Atomic Claim
AWS Trainium software strategy Phase 1 將釋出並 open-source native PyTorch backend。
- Epistemic Mode:
EXPECTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"additional_nodes": [],
"frame_type": "RELATION",
"object": {
"id": "04_knowledge_base/PyTorch",
"label": "PyTorch"
},
"predicate": "OPEN_SOURCES",
"qualifiers": {
"condition_text": "Phase 1 native backend",
"numeric_mentions": [],
"temporal_mentions": []
},
"subject": {
"id": "04_knowledge_base/AWS",
"label": "AWS"
}
}④ Canonical Entity Mapping
⑤ Human Review
請在 Properties 逐項確認：
- 原文 → Atomic Claim 是否忠實
- Atomic Claim → Semantic Frame 是否忠實
- Canonical Entity mapping 是否正確
- Epistemic mode 是否保留原文語氣
- 最後選擇
review_action
Review state
Markdown 內文不是正式 approval。只有 Apply bridge 寫入的 Decision Ledger event 才是正式決策。