Successfully setup an internet CS 1.6 server - what's next?

chinga · **Author**

Hello,

I just managed to successfully setup an HLDS server (CS 1.6) on AWS EC2 instance, and I can connect to it from other computers on the internet
I am using SteamCMD on Ubuntu 20.04 server.
But the only thing that I can use is the SteamCMD console - it's hard to control the server like that.

So I wonder what are the best things I need to do next in order to be able to control my server in a comfortable way.

What scripts will help me setup admins, etc. What protections do I need?
Right now I can only change maps/kick/ban using the SteamCMD console - but I guess that's not the best and easiest way?

Please help me choose the scripts/mods I need to make my server easier to control and protect the server (DDoS, anti-cheat, admin plugins and so on)

After that I'll install the gaming mods I'm looking for (Auto-Mix, public, etc..) - but first I want to be able to control it better

Thanks!

fysiks

SteamCMD is only used to download HLDS, it does not run when the game server is running (so you are referring to the HLDS console).

Most normal functionality while playing is done with AMX Mod X (for changing the map or kicking and banning people) which allows you to do many commands while playing.

If you're looking for something to help manage the HLDS process, you could look into using LinuxGSM. It can be a bit confusing to configure but it works.

chinga

Thank you! Yes. I eventually realized that. Now I'll call it the HLDS console instead.
I installed AMX Mod X successfully although through the installer, because that didn't work manually.

I am running Windows 10 now instead of Ubuntu, I reinstalled it for more comfortable GUI.
I know CS 1.6 server can easily be shut down bye DDoS or similiar attack - what should I do to protect it from that? Is Windows able to protect DDoS? Or I should go back to Ubuntu?

fysiks

No operating system can prevent a DDoS attack. Protecting against this type of attach requires something to intercept traffic that is going to your server. AWS has a feature for this which can be found here (I don't know any specifics since I just looked it up online).