Open FloppyNotFound opened 1 year ago
Thanks for the feedback! Fermyon Cloud doesn't have support for static IP yet, but we'll put this feature into consideration. Do you need the ability to assign a static IP to a specific Spin app, or would an IP range be sufficient?
An IP range would be the minimum requirement for us, as long as it doesn't change - or only after being announced some time ahead so that we are able to reconfigure our firewall in advance.
Thanks for putting this into consideration!
While we may in the future document our IP ranges they won't be isolated to a single user or app, so it isn't ideal as a security feature. One alternative we have discussed would be to provide some sort of authenticating proxy that could be run on your own infrastructure which would only be accessible to your own apps.
Documentation topic (what would you like covered)?
Outbound IP-Address: We have a scenario in which we need to call an external API from our service. This API is behind a firewall, which whitelists certain IPs which should have access to it.
Will it be possible to configure a static IP address, or will there be a static IP range? Will there be additional costs, if so, how is the pricing model for that?
I was having a look at other serverless providers (Azure Functions, Cloudflare Workers), and both only allow static IPs in their (quite expensive) premium plans.
What documentation did you review and why was it not sufficient?
I had a look at several pages in the docs, for example: https://developer.fermyon.com/spin/configuration But I couldn't find any information about outbound IPs.
Thanks in advance!