AWS AmazonCloudWatch documentation change
Summary
Added four new third-party integrations (PingIdentity PingOne, OneLogin Identity, Entrust IDaaS, Drupal Core) to the integration table, all using API method and requiring API caller permissions.
Security assessment
The change expands the list of supported identity providers (IAM platforms) and Drupal Core, which are security-related integrations. It adds documentation about security features but doesn't indicate a specific security vulnerability.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/third-party-integration-setup.md b/AmazonCloudWatch/latest/monitoring/third-party-integration-setup.md index cb6b9d6d0..e3f3300a7 100644 --- a//AmazonCloudWatch/latest/monitoring/third-party-integration-setup.md +++ b//AmazonCloudWatch/latest/monitoring/third-party-integration-setup.md @@ -38,0 +39,4 @@ Cisco Umbrella | S3 Delivery | Yes | Yes | No | [Source-specific IAM policies](. +PingIdentity PingOne | API | No | No | Yes | [API caller permissions](./pipeline-iam-reference.html#api-caller-permissions) +OneLogin Identity | API | No | No | Yes | [API caller permissions](./pipeline-iam-reference.html#api-caller-permissions) +Entrust IDaaS | API | No | No | Yes | [API caller permissions](./pipeline-iam-reference.html#api-caller-permissions) +Drupal Core | API | No | No | Yes | [API caller permissions](./pipeline-iam-reference.html#api-caller-permissions)