AWS AmazonCloudWatch: CloudWatch Omni: telemetry ingestion auth now SigV4 or bearer token
Summary
Revises the encryption/transport section so telemetry ingestion is described as authenticated with Signature Version 4 or a bearer token, and states that unauthenticated (rather than unsigned) requests are rejected with HTTP 403.
Security assessment
The changed line broadens the documented authentication mechanisms for the ingestion endpoint from SigV4-only to SigV4 or bearer token, while clarifying that all unauthenticated requests get 403. This is authentication/access-control documentation for a security-relevant endpoint, but no vulnerability, CVE, or incident is referenced.
Evidence
+Telemetry ingestion is over HTTPS and is authenticated with Signature Version 4 or a bearer token. Unauthenticated requests are rejected with an HTTP 403 response.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/omni-data-encryption-in-cloudwatch-omni.md b/AmazonCloudWatch/latest/monitoring/omni-data-encryption-in-cloudwatch-omni.md index 8dae9bb..629716d 100644 --- a//AmazonCloudWatch/latest/monitoring/omni-data-encryption-in-cloudwatch-omni.md +++ b//AmazonCloudWatch/latest/monitoring/omni-data-encryption-in-cloudwatch-omni.md @@ -265 +265 @@ All communication with CloudWatch Omni service endpoints uses HTTPS with TLS. Th -Telemetry ingestion is over HTTPS and is authenticated with Signature Version 4\. Unsigned requests are rejected with an HTTP 403 response. +Telemetry ingestion is over HTTPS and is authenticated with Signature Version 4 or a bearer token. Unauthenticated requests are rejected with an HTTP 403 response.