+1 that's a critical feature. Without it our staging and dev environments can be accessed by hackers.

Would also find this incredibly useful, both for locking down SSH access and for certain web services that are for our internal use only

Being able to have Preview Environments and Staging environment behind a VPN to limit access is essential for us. Would love to see this happening.

+1 to this. It'd be nice to limit SSH access to machines similar to how we can limit access to DBs in Render.

Also needed for company VPN / staging instances etc. This is potentially something that will make us churn off of render.

I'd also appreciate to have that feature in place soon

Our use case is simple: we want to offer our clients with bot running out of Render, but they're worried about security. Having a, say, Flowise or Botpress web service allowed to run only on a specific website IP will limit the chances of cloning or accessing the service outside the IP

We would love to be able to do this for the purposes of implementing a WAF or API protection for a container. Without the local IP source restriction, the environment is still vulnerable to scans and attacks. Thanks for the consideration!

We have a use case where our render web service is setup as an origin for CDN/WAF web proxy. This feature would be really useful to restrict IP access to the origin so only the allowed egress from CDN/WAF service can interact with our web service.