# Fly-Instance-Id header alternative for websockets

**URL:** <https://community.fly.io/t/fly-instance-id-header-alternative-for-websockets/7536>\
**Category:** Questions / Help\
**Created:** [September 29, 2022, 5:12pm UTC](https://community.fly.io/t/fly-instance-id-header-alternative-for-websockets/7536 "2022-09-29T17:12:35Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![ignoramous](https://avatars.discourse-cdn.com/v4/letter/i/a9adbd/32.png) [@ignoramous](https://community.fly.io/u/ignoramous)\
**Post date:** [October 1, 2022, 6:08pm UTC](https://community.fly.io/t/fly-instance-id-header-alternative-for-websockets/7536/5 "2022-10-01T18:08:42Z")

</div>

> [@mdj](#):
>
> you need to tell [fly.io](http://fly.io) that you want VMs running in each region:

One could consider deploying [Machine apps](https://community.fly.io/t/were-launching-fly-machines-today/5305) instead, if one wants to break free of their [Nomad orchestration](https://community.fly.io/t/standard-autoscale-not-placing-vms-in-each-region/6846/5).

There are [rough edges](https://community.fly.io/t/preview-deploying-applications-on-machines-with-flyctl/6171), notably with [how traffic is spread over to Machines](https://community.fly.io/t/preview-postgres-on-machines-fly-apps-v2/7483/2) by Fly proxy and a lack of clarity [around health checks](https://community.fly.io/t/how-do-i-change-the-restart-policy-for-machines/7341/8), but things can only improve from here on out.

---

_[View the full topic](https://community.fly.io/t/fly-instance-id-header-alternative-for-websockets/7536)._