A robotics manufacturer needs to run containerized quality-inspection workloads inside its factory with single-digit millisecond access to on-site machines, using AWS APIs and EKS while AWS operates the rack hardware. Which hybrid compute pattern satisfies this low-latency on-premises requirement with managed infrastructure?
Select an answer to reveal the explanation.
Short Explanation
When milliseconds matter and you don't want rack duty, location is everything. AWS Outposts brings AWS compute into your building with AWS minding the metal.
Full Explanation
AWS Outposts provides AWS-managed racks installed on premises, exposing EC2, EKS, ECS, and storage with the same APIs and console as the Region, which keeps inference and control loops local for single-digit millisecond access while offloading hardware maintenance. EKS Anywhere fails by concept because it delivers consistent Kubernetes software on customer-managed hardware, leaving rack procurement and maintenance to the factory rather than providing managed infrastructure. Local Zones fail by concept because they place AWS infrastructure in a nearby metro, which improves latency over Regions but does not reside inside the factory for on-site machine adjacency. ECS Anywhere fails by concept because it extends ECS control to existing VMs without delivering low-latency AWS hardware or EKS conformance on site. Exam caveat: choose Outposts when AWS must operate the hardware on premises, Anywhere when you keep hardware. Practical check: validate power, networking, and machine connectivity requirements for the Outposts rack order.