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.
In other words their response was “hey dumbass here’s what happened, now move along”. They didn’t do anything except school you.
Dude there is a weird disconnect going on in the comments. Yes bots are thing, yes services are abused, yes not everyone plays nice on the Internet, yes you can’t control what traffic comes in. I know I’m going to be seeing more this and yes I’m obviously not going to be responding to every one of them.
It was my brand new server’s first and I felt like celebrating the event by filling out the AWS abuse form. It was literally copy and paste.
Also, I’m not fussed about what ever services they are running. I didn’t ask for it or want it. I told them as much and I going to leave it at that.
No one got schooled. There is nothing wrong with telling someone who shows up at your business to please don’t come back. Y’all need to chill.
Well this whole thing was fun but I’m going to get on with my day
I don’t think anyone here disagrees that port scanning is bad, nor that you even filed an aws ticket. And congrats on your live service.
But your answers to comments are weird, like this is not only your first server or vps experience with a public interface, but your first time exposing anything to the public web. And even if that’s true, there’s a first time for everyone.
But man, doubling down and insisting that “port scanning is unauthorized traffic” betrays a certain naivete about how tcpip works.
What you are seeing is not only normal, but AWS can’t do anything about it because that’s how IP source and destination sockets work.