AWS's Open-Source Physical AI Toolchain Names Five Stages and Four NVIDIA Parts, but Its Solutions Page Lists No Licence or Repository

Amazon Web Services launched an open-source Physical AI Toolchain for roboticists on Oct. 8, according to The Robot Report. The AWS page for the guidance it points to, Guidance for Physical AI for Robotics on AWS, lists no licence, links no repository, gives no price and carries no release date. The only date on it is the 2026 copyright line.

Five stages, two suppliers

The toolchain runs from synthetic data generation through model training, simulation and validation, and edge deployment, to continuous improvement, per The Robot Report. AWS supplies Amazon SageMaker for training and AWS IoT Greengrass for distributing models to edge devices. NVIDIA supplies Isaac Sim, Isaac Lab, Isaac GR00T and Cosmos.

Supplier	Named parts	Role given
AWS	Amazon SageMaker	Model training
AWS	AWS IoT Greengrass	Distributing models to edge devices
NVIDIA	Isaac Sim, Isaac Lab, Isaac GR00T, Cosmos	No per-stage mapping in either source

Neither source says which NVIDIA part handles which of the five stages, and we have not inferred it. The AWS page names only "NVIDIA's physics engine" for simulation-based training.

What the page does not say

The AWS page is a Solutions Library guidance. It says the sample code is provided under the AWS Customer Agreement or a separate written agreement, and that it is not meant for production accounts or critical data. It warns that deploying the content may incur AWS charges, such as for EC2 instances or S3 storage. That language belongs to a reference architecture, which is a different thing from the project The Robot Report describes as open source.

The two are possibly the same release, described from two angles. The reporting available does not settle it. A reader looking for the code should look for the repository before planning around the label.

Hardware-neutral, by design

Sri Elaprolu, Director of Frontier AI Science and Engineering at AWS, said "The toolchain is intentionally staying neutral to that final step." The final step is the robot. The toolchain stops at the edge device, which is what lets AWS skip the question of whose arms and legs run the model.

Elaprolu said it draws on lessons from Amazon's robotics operations, which include more than 1 million robots. The Robot Report also cites RLWRLD, a South Korean company that worked with AWS on a tactile sensing model for five-finger dexterity tasks, and Bedrock Robotics, which trains models for autonomous construction equipment on AWS. It notes Telexistence has deployed more than 300 humanoids in convenience stores. None of those is described as a user of this toolchain.

The RoboMaker gap

The toolchain is not a direct replacement for AWS RoboMaker, which AWS shut down in 2025, per The Robot Report. Elaprolu described RoboMaker as one component of AWS's robotics stack. That leaves roboticists who built on RoboMaker without a named migration path in either source.

What would change this read

A GitHub repository with a licence file would settle the open-source question in one commit. A published price for a training run would settle the cost question; today the only cost guidance is that AWS charges may apply. Until then the Oct. 8 launch is a description of intent from a trade publication and a reference-architecture page. For other robotics reporting, see Boston Dynamics' Atlas plan and Mecka AI's robot-training data round.