Security Measures and Billing Protection for Deployed Services
Imagine a scenario my deployed services were attacked. Cost by service increases with the activity of usage. So my billing invoice dramatically increases to ginormous cost.
Has described higher issue a place to be?
If it has, are there any solutions Railway provides to protect services from such attacks? Or maybe you can give some recommendations to avoid this problem.
In a worst-case scenario. My services fell victim to an attack and I was billed incorrectly (taking into account the hacker attack), would I be held responsible for the entire amount? Are there avenues to reach out to support in order to address this matter?
Hope to see your answer soon, thanks for your attention to my issue.
5 Replies
Project ID:
2355a60c-fb4a-435c-b599-002301157e412355a60c-fb4a-435c-b599-002301157e41
I’m not sure if Railway offers anything, but clearly stated in their TOS ( https://railway.app/legal/terms );
You will not share your Railway User ID, account or password with anyone, and you must protect the security of your Railway User ID, account, password and any other access tools or credentials. You’re responsible for any activity associated with your Railway User ID and account.
Railway
Terms of Service
Railway is an infrastructure platform where you can provision infrastructure, develop with that infrastructure locally, and then deploy to the cloud.
The problem stands not in how to secure my railway account. The core issue revolves around the security of services hosted on the Railway platform. For instance, consider a situation where a service, such as a webpage or RESTful API, deployed on the Railway, becomes the target of attack with many and many requests. This leads to my billing invoice dramatically increasing to ginormous cost.
you want this then
https://www.cloudflare.com/en-gb/ddos/
but to answer another question, yes you would be on account to pay your large bill if you decide not to use cloudflare (or similar service)