AWS guardduty documentation change
Summary
Fixed a typo in the description of RDS Protection functionality (changed 'm anomalous' to 'anomalous')
Security assessment
This is a minor typographical correction with no security implications. The change doesn't introduce new security information, address vulnerabilities, or modify security-related functionality. It simply fixes a spelling error in existing documentation about RDS Protection's login attempt monitoring.
Diff
diff --git a/guardduty/latest/ug/rds-protection.md b/guardduty/latest/ug/rds-protection.md index 887cee1a5..aff294877 100644 --- a//guardduty/latest/ug/rds-protection.md +++ b//guardduty/latest/ug/rds-protection.md @@ -19 +19 @@ RDS for PostgreSQL read replica instances require the primary database instance -RDS Protection doesn't require additional infrastructure; it is designed so as not to affect the performance of your database instances. When RDS Protection detects a potentially suspicious or m anomalous login attempt, GuardDuty generates one or more [RDS Protection finding types](./findings-rds-protection.html) with details about the potentially compromised database. +RDS Protection doesn't require additional infrastructure; it is designed so as not to affect the performance of your database instances. When RDS Protection detects a potentially suspicious or anomalous login attempt, GuardDuty generates one or more [RDS Protection finding types](./findings-rds-protection.html) with details about the potentially compromised database.