Announcing Tower’s first US region: Compute Where Your Data Lives

At Tower, our architecture is built on a strict separation between the control plane (where decisions are made about when and where to run your Python apps) and the data plane (where the actual data access and processing happens). This flexibility allows us to bring the compute directly to your data. Today, we are thrilled to announce our newest expansion: the us-east-1 Data Plane is now generally available. By introducing a AWS us-east-1 data plane alongside our existing AWS eu-central-1 infrastructure, we are unlocking new capabilities for teams that require their data to remain within US data centers.

Why We Built This This expansion introduces a powerful new use case specifically centered around data locality. If your core data lives in an AWS us-east-1 database, processing it in our European data plane previously meant piping it across the Atlantic. While effective, transferring massive datasets across Amazon’s fiber incurs egress fees and introduces latency.

By executing your Tower runs in the same region where your data already lives, you can:

Eliminate egress fees associated with cross-ocean data transfers.
Reduce latency by avoiding fiber transit times.
Meet customer requirements for data processing within US borders (ensuring compliance for your own customers' needs).

How to Enable AWS us-east-1 for your Team

Switching your execution region requires zero heavy lifting and is available to all users immediately. This is a Team-level setting, meaning you can seamlessly run multi-region operations, like processing US data for one team and EU data for another, all from the exact same account.

Navigate to your Team Settings in the Tower app.
Locate the Execution Region option.
Toggle the setting from AWS eu-central-1 to AWS us-east-1.

All future runs will instantly route to the new US data plane.

Best Practices for an AWS us-east-1 transition

To get the most out of this new capability, keep a few operational details in mind:

Mind Your Data's Zip Code: Switching your execution region to AWS us-east-1 does not automatically migrate your existing data. Ensure the data you are actively processing is actually located in the US to avoid accidentally pulling data from the EU, which could incur unexpected costs.
Update Your Network Rules: If your infrastructure (like a Postgres database or an S3 bucket policy) restricts access to specific IP addresses, you will need to update your allowlists. We have two new dedicated IP addresses for the AWS us-east-1 egress that must be whitelisted to ensure uninterrupted connectivity. See our docs for more info on that.

The launch of our us-east-1 data plane is just the beginning of our global expansion. Log in to app.tower.dev today to check out your new regional settings! Have an opinion on which region or cloud provider we should tackle next? Join our Discord community and let us know.