AWS redshift: Update user lockout feature to Patch 208
Summary
Corrects the Redshift patch version that introduces automatic user lockout after consecutive failed login attempts from Patch 204 to Patch 208, in both the summary bullet and the section heading/body.
Security assessment
The change only updates the patch version number for an existing brute-force/login-lockout security feature; it documents a security control (lockout after failed logins, default threshold 5) but does not address a specific vulnerability or incident.
Evidence
+ * Amazon Redshift enforces user lockout after multiple failed login attempts starting with Patch 208
Diff
diff --git a/redshift/latest/mgmt/behavior-changes.md b/redshift/latest/mgmt/behavior-changes.md index bfa7033..819dc2d 100644 --- a//redshift/latest/mgmt/behavior-changes.md +++ b//redshift/latest/mgmt/behavior-changes.md @@ -27 +27 @@ The following describes upcoming behavior changes. - * Amazon Redshift enforces user lockout after multiple failed login attempts starting with Patch 204 + * Amazon Redshift enforces user lockout after multiple failed login attempts starting with Patch 208 @@ -121 +121 @@ For more information, see [Controlling access to AWS KMS keys](https://docs.aws. -### Amazon Redshift enforces user lockout after multiple failed login attempts starting with Patch 204 +### Amazon Redshift enforces user lockout after multiple failed login attempts starting with Patch 208 @@ -123 +123 @@ For more information, see [Controlling access to AWS KMS keys](https://docs.aws. -Starting with Amazon Redshift Patch 204, to enhance the security posture of your data warehouse, Amazon Redshift automatically locks a database user after it exceeds the configured number of consecutive failed login attempts. The feature is enabled by default with a threshold of 5 failed attempts (configurable from 2 to 50) and applies to both provisioned clusters and serverless workgroups. +Starting with Amazon Redshift Patch 208, to enhance the security posture of your data warehouse, Amazon Redshift automatically locks a database user after it exceeds the configured number of consecutive failed login attempts. The feature is enabled by default with a threshold of 5 failed attempts (configurable from 2 to 50) and applies to both provisioned clusters and serverless workgroups.