# Region scaling configuration

**URL:** <https://community.fly.io/t/region-scaling-configuration/5961>\
**Category:** General\
**Created:** [July 12, 2022, 5:50am UTC](https://community.fly.io/t/region-scaling-configuration/5961 "2022-07-12T05:50:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jerome](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/jerome/32/17_2.png) [@jerome](https://community.fly.io/u/jerome)\
**Post date:** [July 12, 2022, 2:36pm UTC](https://community.fly.io/t/region-scaling-configuration/5961/2 "2022-07-12T14:36:36Z")

</div>

It’s a bit hard (if not impossible) to provision in the way you described with our current infrastructure.

However, it should be possible with [our new “machines” platform](https://fly.io/blog/fly-machines/). It should give you precise control of where you’re deploying each of your instances.

I don’t think the docs are up-to-date for them, but you can find a lot of info with `fly machines --help`.

It doesn’t currently work with `fly deploy`, but we’re working on that. This means you’ll have to update all your machines one-by-one to make any kind of change.

There are also rough edges with it, but it’s improving every day.

---

_[View the full topic](https://community.fly.io/t/region-scaling-configuration/5961)._