Allow Network Peering to be used by Atlas Triggers / Realm Apps
What is the problem that needs to be solved? Some users want to receive outgoing network connections (e.g. with HTTP/HTTPS traffic) from Atlas (Atlas Triggers / Realm Apps) via their configured Network Peering, i.e. via private IP address space (so that everything is kept in private IP address space and nobody outside could reach it). Example: customer would like to have Atlas Trigger / Realm App which will notify (via HTTP) some of customer's internal system(s) about a change/trigger.
Why is it a problem? (the pain) Current Atlas (Atlas Triggers / Realm Apps) behavior does not allow to use private IP address space for such outgoing network connections.
4
votes
![](https://secure.gravatar.com/avatar/780232e12b5c41adc3bc37e6438624b8?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)