Nice big old port scan. Brand new server too. Just a few days old so there is nothing to find. Don’t worry I contacted AWS. Stay safe out there.
Nice big old port scan. Brand new server too. Just a few days old so there is nothing to find. Don’t worry I contacted AWS. Stay safe out there.
Yes. Don’t port scan my shit.
Umm…
You know how that works, right? Like, if you don’t want to expose ports, just… don’t expose them. But you can’t prevent port scanning.
I would love to see the support request from AWS for this.
Edit: also, I think “script kiddy” is a bit of a stretch here.
I don’t have any open ports. I do not care if I did. Port scanning is not authorized traffic.
Here you go:
In other words their response was “hey dumbass here’s what happened, now move along”. They didn’t do anything except school you.
Hahahahahaha
And?
I think they have a LOT to learn about how the internet ‘works’ as well as how the internet works.
Thing is, for the average consumer of the internet, they have no real concept what’s going on behind the webpage with the fancy graphics they happen to be looking at. When I try to explain to them that bots comprise conservatively 40-50% of all internet traffic which is about ~2 zettabytes per 24 hour period, they still don’t get it. And really, they don’t have to, that’s the job of sysadmin. It’s still pretty mind blowing.
And abuse forms get filled out
Bro. AWS can do jack shit, that’s not how it works. You might as well call Toyota next time you see a Camry speeding. All you’re going to do is annoy people who in no way can help you with a problem that is your responsibility. I can guarantee they’ll tell you you should use private VPCs and entrypoints with security groups, which is what every AWS tutorial starts out by telling you to use.
Lol what
I think you should read the terms of your AWS contract. How do you think aws moves instances if not for agents gathering metrics?
And this case is Mandiant, so you’re fine.
Are you sure you’re ready for AWS?
Not on AWS