AWS AmazonCloudWatch documentation change
Summary
Rephrased recommendation for using the file audit device in HashiCorp Vault
Security assessment
Change is a minor wording improvement without security context. No vulnerability or security feature is mentioned.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/hashicorp-vault-source-config.md b/AmazonCloudWatch/latest/monitoring/hashicorp-vault-source-config.md index b94e4cb2b..d5cec15ca 100644 --- a//AmazonCloudWatch/latest/monitoring/hashicorp-vault-source-config.md +++ b//AmazonCloudWatch/latest/monitoring/hashicorp-vault-source-config.md @@ -30 +30 @@ HashiCorp Vault integration uses Amazon S3 and Amazon SQS to ingest log data int -HashiCorp Vault audit logs can be forwarded to Amazon S3 using the Vault file audit device combined with Fluent Bit. Vault supports three audit device types: **file** , **socket** , and **syslog**. The **file** audit device is recommended for highest reliability. +HashiCorp Vault audit logs can be forwarded to Amazon S3 using the Vault file audit device combined with Fluent Bit. Vault supports three audit device types: **file** , **socket** , and **syslog**. We recommend the **file** audit device for highest reliability.