Which other states/regions outside of Ohio are part of the us-east-2 region?

You can think of an AWS region as a set of closely located, but independent, data centers. You can assume that the data centers are all in the same metropolitan area several miles apart, though I'd have to do some searching to know exactly what guarantees AWS provides. Regardless of the details, there are no states or regions that are "part of" an AWS region; the AWS region us-east-2, rather, is physically located in the state of Ohio and is accessible from anywhere in the world (with Internet access).

From a cost perspective, AWS charges for data that leaves a region; it doesn't matter if it is going across the street, to a neighboring state, or across the world. Latency may be a different question, but if your application is latency-sensitive enough to care about the difference between data transfer to Cleveland, Pittsburgh, or Chicago, you may want to consider sticking within the AWS region itself.

-- Jeff

Each AWS region is (for the purposes of this discussion) an entity in its own right. All other regions (whether they are in the US or not) are separate regions and there will be inter-region data transfer charges when communicating with those regions.

For background, AWS specifically designs regions as separate entities deliberately in order to make each region independent of other regions. From the Global Infrastructure page:

Each region is fully isolated and comprised of multiple AZs, which are fully isolated partitions of our infrastructure. To better isolate any issues and achieve high availability, you can partition applications across multiple AZs in the same region. In addition, AWS control planes and the AWS management console are distributed across regions, and include regional API endpoints, which are designed to operate securely for at least 24 hours if isolated from the global control plane

AWS charges for data egress, which is the transfer of data out of their services to the internet or other AWS regions. However, within the same region, data transfer is typically free or significantly cheaper, especially when considering services like Amazon EC2 and Amazon S3.

Given that your data is stored in the us-east-2 region and you want to avoid large data egress costs, your best option is to position your private GPU cluster in a location that has physical proximity to the AWS us-east-2 data centers to minimize latency, but without moving the data out of the us-east-2 region to avoid egress fees.

The us-east-2 region for AWS is located in Ohio. Given this, any location in or near Ohio would be ideal for your private GPU cluster.

Suitable US States/Regions:

Ohio itself – being in the same state as the us-east-2 region will provide you with the lowest possible latency. Surrounding States: States surrounding Ohio will also offer relatively low latency. These include: Indiana Kentucky West Virginia Pennsylvania Michigan When establishing your private GPU cluster:

Ensure a high-speed and reliable internet connection. Consider using Direct Connect if you anticipate high data throughput. AWS Direct Connect provides dedicated network connections from on-premises or colocation environments to AWS. While the list above mentions states that are physically closer to the us-east-2 region, latency can be influenced by other factors such as the quality of your internet connection, ISPs, and network routing. Thus, it might be beneficial to test the network latency from potential sites to the us-east-2 region. Finally, if you're using EKS Anywhere, it's designed to run Kubernetes clusters in any location, including on-premises, so it should work smoothly with your private GPU cluster in or near Ohio.

Remember, while proximity helps reduce latency, the primary objective here is to avoid data egress costs. Ensure that any data transfers remain within the AWS us-east-2 region boundaries. To get more help you can checkout https://tekdash.com