AWS AmazonRDS documentation change
Summary
Removed section about Aurora Serverless v1 log upload procedures
Security assessment
This change removes documentation about how Aurora Serverless v1 handles CloudWatch log uploads. While logging is important for security monitoring, this appears to be documentation cleanup for a deprecated feature rather than addressing a security vulnerability.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.CloudWatch.md b/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.CloudWatch.md index 4772eab88..aa44b084e 100644 --- a//AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.CloudWatch.md +++ b//AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.CloudWatch.md @@ -25,4 +24,0 @@ If you use this alternative method, you must have an IAM role to access CloudWat - * The procedure is slightly different for Aurora Serverless v1 DB clusters than for DB clusters with provisioned or Aurora Serverless v2 DB instances. Aurora Serverless v1 clusters automatically upload all of the logs that you enable through configuration parameters. - -Therefore, you turn on or turn off log upload for Aurora Serverless v1 DB clusters by turning different log types on and off in the DB cluster parameter group. You don't modify the settings of the cluster itself through the AWS Management Console, AWS CLI, or RDS API. For information about turning on and off MySQL logs for Aurora Serverless v1 clusters, see [Parameter groups for Aurora Serverless v1](./aurora-serverless-v1.how-it-works.html#aurora-serverless.parameter-groups). -