1 Answer
- Newest
- Most votes
- Most comments
1
Make sure that the security group is not allowing traffic from 0.0.0.0/0. That could indicate that you are getting brute forced and the instance has a hard time keeping up with all connection requests. If you are using Linux, you can install a tool like fail2ban which will automatically create firewall rules to block traffic from ip's that attempt to authenticate with invalid credentials.
If you truly believe that there is something wrong with your account, then you can open a ticket to the billing team as your repost link you referenced says.
Relevant content
- asked 4 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
this is a good point but it's unlikely that I am being brute forced every time after EC2 is up for about the same time.