Mallory Gershenfeld

For data-intensive workloads such as ML training, analytics, and AI search, every millisecond spent waiting on data costs money without advancing the work. When workloads make millions of small, random reads and writes, low-latency storage keeps compute productive without provisioning for peak demand.

Countries around the world are increasingly introducing or updating data residency and digital sovereignty laws that require at least one copy, or sometimes all data, to be stored or processed in a specific geographic or sovereign location. This introduces new challenges for customers.

While most workloads can run in AWS Regions, some workloads have to remain in a particular jurisdiction for regulatory or contractual reasons. When an AWS Region does not exist within that jurisdiction, organizations need other options to run their workloads on the cloud.

You want to use AWS infrastructure and services, but have workloads that can’t move to the cloud. You have remote operations that need storage, but have no Internet access, or you require low-latency access to on-premises systems, or you have data residency requirements that specify where to store your data.