Repeated login attempts in the log file for an RDS instance

0

In the log file for our RDS DB Instance the Error log file is full of the following entries

2023-10-05 06:08:26.46 Logon Error: 18456, Severity: 14, State: 5. 2023-10-05 06:08:26.46 Logon Login failed for user 'server'. Reason: Could not find a login matching the name provided. [CLIENT: 14.45.33.45] 2023-10-05 06:08:29.01 Logon Error: 18456, Severity: 14, State: 5. 2023-10-05 06:08:29.01 Logon Login failed for user 'server'. Reason: Could not find a login matching the name provided. [CLIENT: 14.45.33.45] 2023-10-05 06:08:31.64 Logon Error: 18456, Severity: 14, State: 5. 2023-10-05 06:08:31.64 Logon Login failed for user 'server'. Reason: Could not find a login matching the name provided. [CLIENT: 14.45.33.45] 2023-10-05 06:08:32.64 Logon Error: 18456, Severity: 14, State: 5. 2023-10-05 06:08:32.64 Logon Login failed for user 'SHRISHTI'. Reason: Could not find a login matching the name provided. [CLIENT: 45.135.232.28] 2023-10-05 06:08:33.07 Logon Error: 18456, Severity: 14, State: 5.

This is happening approximately every 2 seconds.

Is there anyway I can stop this?

Ian
질문됨 8달 전195회 조회
2개 답변
0
수락된 답변

It seems your RDS is publicly facing. If this is not required, disable public access.

If it is, lock down your security group to only allow connections from trusted IP addresses.

profile picture
전문가
답변함 8달 전
profile pictureAWS
전문가
검토됨 8달 전
0

Possibly got brute-force login attempts from attackers. Is your DB instance accessible via the Internet? If so, you need to either modify your DB subnet group to use private subnets or change its security group's inbound rule to restrict allowed IP.

profile picture
HS
답변함 8달 전
profile pictureAWS
전문가
검토됨 8달 전
  • Thank you I had an inbound rule accepting all connections. I have deleted this rule so I only have one inbound rule with a restricted IP address. Thank you

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠