71–75 of 75 posts
Earlier quoted context omitted.
If you are not using Python, scanning large swaths of IP addresses or even the whole IPv4 space for open port 9200 is very doable.
What's the problem with Python in this situation? Concurrency and Gil locks?
Earlier quoted context omitted.
"it doesn't take a genius to set up a password for a cloud service." Where are you going to store the password? I'm not saying it's rocket science but it does take consideration. Do you store it in a plain text file on the server? How do you deal with CI/CD? Do you run a separate service for one credential?
Really simple solutions. AWS itself has a Secrets Manager from which other authorized services can pull secrets. If it's an outside CI/CD platform then those usually also have a place to store credentials.
Don't get me wrong. I don't think anyone should skip this step. You need auth for your datastores.
Earlier quoted context omitted.
The Docker container is using a separate network namespace with a separate virtual interface that packets are routed to. The "PREROUTING" chain runs before the "INPUT" chain so yes, the rules you put in "INPUT" won't apply.
Its rules also go into the "nat" table instead of the "filter" table. Use "iptables -L -t nat" to display them.
Network layering is still important on the cloud but many DevOps appear to miss that. Logical cloud protection layers - like security groups - are an additional security layer but not a replacement for proper route design.
Earlier quoted context omitted.
> you only need to fake competence to management With so many 10x full-stack developers who're just looking to get sh done and clock out, it can't be otherwise. If managing a server becomes just another bullet point in a developer job, this is exactly what we get. Sure I can deploy stuff, but you shouldn't trust me. Unfortunately many are not so honest or even aware of the complexity (unknown unknowns).
> If managing a server becomes just another bullet point in a developer job, this is exactly what we get. Yup...the same management are the ones that laid off the DBAs, system admins, network engineers, etc because "the cloud" hand waves all this stuff away now.