12 days ago
For a Railway service/container, is there any platform-level mechanism that can enforce true deny-all outbound network egress for that service and every child process it spawns, independently of application code?
We require a security boundary that cannot be bypassed by the workload itself.
Private Networking is not sufficient because it concerns internal service-to-service connectivity, and Static Outbound IPs are not an egress-denial mechanism.
If Railway supports true deny-all outbound egress, please identify:
- the exact Railway feature or configuration;
- whether it applies to the entire process tree, including child processes;
- whether the workload itself can alter or bypass the restriction;
- whether it can be enforced without relying on application code.
If Railway does not currently support this, please confirm that clearly in writing.
1 Reply
12 days ago
The outbound networking features we offer are Static Outbound IPs, which give a service consistent IP addresses for allowlisting with third parties, and Private Networking for service-to-service traffic. Neither is a deny-all egress control.
We have not verified a service-level setting that blocks all outbound internet traffic for a container and its child processes independently of the workload, so we can't point you to a feature, scope, or bypass guarantee that meets the security boundary you described.
Status changed to Awaiting User Response Railway • 12 days ago
5 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 5 days ago