Most important question : can machines be balanced this way : 1 request = 1 machine, if no machine available, an error is thrown ?
Can endpoint be protected ? Our backend, that is not on fly.io, needs to call http endpoint to start machines, but we don’t want that random http request call our endpoint and start machines. I guess I could set up a proxy on fly.io to handle such auth mechanism, but frankly I would prefer avoid it…
How many machines/resources can we use ?
Regarding securing endpoint, I would like that our backend calls for example https://myapp.fly.dev . When http request ended, then worker finished its task. But if any random web bot call this URL (as we often see in server logs), it will start a machine, and we will be billed accordingly…
For machines amount, for tests, it’s ok for now, but for production, we will use sometimes dozens of machines (1 proc with 1/2 GB each request).
Regarding SDK, I guess we don’t need it ATM thanks to http endpoint functionnality.
To prevent random bots from being able to wake up your machines I’d say remove public IP addresses from that machine and work with a Flycast IP (make sure to have a services section!) since it can wake your machine on HTTP.
Its gonna be really easy if it’s a Fly machine calling a Flycast IP because our networking Just Works but if you need to call that machine from your Not-on-Flyio server you’d probably want to connect it to Fly using Wireguard which is easy and also Just Works .
Hi, I am building a product that’ll run user code in machines and I can’t predict how many I’d need. So what is this soft limit you talk about? how many?
Do I get email when I’m reaching 80% of this limit?