Skip to content

Commit 33fa145

Browse files
committed
changelog
1 parent cc1bdf9 commit 33fa145

File tree

1 file changed

+41
-0
lines changed

1 file changed

+41
-0
lines changed
Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
title: New Placement Hints for Workers
3+
description: You can now explicitly place Workers close to your existing cloud infrastructure in order to minimize network latency to existing services and databases.
4+
products:
5+
- workers
6+
date: 2025-11-20
7+
---
8+
9+
import { WranglerConfig } from "~/components";
10+
11+
You can now configure Workers to run close to your infrastructure in legacy cloud regions in order to minimize latency to existing services and databases, especially in cases where you have multiple round-trips.
12+
13+
To set a placement hint, set the `placement.region` property in your `wrangler.jsonc` (or `wrangler.toml`) configuration file:
14+
15+
<WranglerConfig>
16+
17+
```jsonc
18+
{
19+
"placement": {
20+
"region": "aws:us-east-1"
21+
}
22+
}
23+
```
24+
25+
</WranglerConfig>
26+
27+
Placement hints support GCP and AWS region identifiers, and will run your Workers in the [Cloudflare datacenter](https://www.cloudflare.com/network/) with the lowest latency to the specified cloud region.
28+
29+
This is an extension of [Smart Placement](/workers/configuration/smart-placement/), which automatically places your Workers closer to the backend APIs based on measured latency. When you don't know the location of your backend APIs, and/or where there are multiple backend APIs, we recommend setting `mode: "smart"`:
30+
31+
<WranglerConfig>
32+
33+
```jsonc
34+
{
35+
"placement": {
36+
"mode": "smart"
37+
}
38+
}
39+
```
40+
41+
</WranglerConfig>

0 commit comments

Comments
 (0)