Uh sorry dude, but no this isn't a script kiddy, these are bots that scan every IP address every day for any open ports, it's a constant thing. If you have a public IP, you have people, govs, nefarious groups scanning it. AWS will tell you the same as if you were hosting it locally, close up the ports, put it on a private network. Use a vpc and WAF in AWS' case.
I get scanned constantly. Every hour of every day dark forced attempt to penetrate our defences.
Not on AWS and yes I know I can't stop port scanning and bad traffic is a thing. Doesn't stop me from filling out the form. I think to piss off you and the other commenters, I'll write a script to auto fill out AWS abuse forms. Also script kiddy or bot, all the same to me, their hosting provider is getting a message from me
Good luck with that, I suppose. Botnets can have thousands, if not hundreds of thousands of infected hosts that will endlessly scan everything on the interwebs. Many of those infected hosts are behind NAT's and your abuse form would be the equivalent of reporting an entire region for a single scan.
I mean go for it? They literally can't do anything, you might as well complain that fire is hot though. It's part of being in the Internet. They provide safety gloves, via VPCs and firewalls, but if you choose not to use them then.. yeah I mean youre probably gonna get burned
Not on AWS and yes I know I can’t stop port scanning and bad traffic is a thing. Doesn’t stop me from filling out the form.
On occasion, if they end up in recidive, I'll report them to AbuseIPdb. If I did it for all attempts, I'd be as busy as a squirrel in a nut factory, because the bots are thick out in the ether. Like every minute of the day they're out there throwing rocks at the castle wall. I had to start logrotating because logs were getting so big it was difficult to review and audit. Every so once in a while, they'll break out the trebuchet and lob something significant, but I've had no breaches to date.
My servers are single user only, so buttoning things down is a little less complicated for me.
I realize you're inexperienced and excited, but this is truly no big deal. Port scans are quite common and aren't even always malicious. You can use nmap to scan systems yourself - just to see what's out there or to test if your firewalls are woking, etc.
If I showed you my WAN-side firewall logs you'd have a panic attack. I have a /29 block and about 10 scans tap one IP or another every second. It's part of being on the internet.
Your domestic home router experiences the exact same thing. Every moment of every day.
Will you report every scan? Every Chinese IP? Every US IP? It's completely common place to have someone 'knock on the door'.
Get off IPv4 anyway and onto IPv6. Good luck to them finding you by chance in there.
For SSH it will have to be attempted connections. Ain't no way I'm putting a forward facing SSH. I'll deal with any downtime that comes from not being able to access my server remotely
I am reminded of a Richard Pryor skit in which he tells about a football player he knew who bit the fingers off of an opponent who was trying to gouge his eyes through his helmet. When Pryor asked him why he bit the guy's fingers off he said 'Everything outside the mask is his. Everything inside the mask is mine.'