- Newest
- Most votes
- Most comments
One thing I observed here with hands-on activity: when we use the Amazon WorkSpaces client to log in to the WorkSpaces, the EventBridge rule successfully captures the events and sends them to the target. But, when we use a third-party platform, in my case, it is Windows App (previously known as Remote Desktop) - the EventBridge rule fails to capture the login event, not as a failed invocation event, either.
As per this documentation,workspacesClientProductNamefield supports only the following values:
- Amazon WorkSpaces Mobile client — iOS client
- WorkSpaces Mobile Client — Android clients
- WorkSpaces Chrome Client — Chromebook client
- WorkSpacesWebClient — Web Access client
- AmazonWorkSpacesThinClient — Amazon WorkSpaces Thin Client device
- Teradici PCoIP Zero Client, Teradici PCoIP Desktop Client, or Dell Wyse PCoIP Client — Zero Client
As a solution, we can configure the CloudWatch agent on AWS WorkSpaces and enable security events (Windows) to capture authentication-related events.
Your assertion that EventBridge cannot capture AWS WorkSpaces login events is incorrect. Amazon WorkSpaces can indeed send events to Amazon EventBridge, including user login events. However, there are a few things to consider that might explain why you're not seeing the expected results:
-
Event Source: WorkSpaces sends events to EventBridge both directly and through AWS CloudTrail. The event pattern you've provided is correct for events sent directly by WorkSpaces.
-
Region Specificity: EventBridge rules and the events they monitor must be in the same AWS region. Ensure that your rule is created in the same region where your WorkSpaces are running.
-
Permissions: Make sure that EventBridge has the necessary permissions to write to your CloudWatch log group. This is typically handled automatically when you set up the rule through the AWS Management Console, but if you're using the AWS CLI, you might need to set up a resource-based policy manually.
-
Event Delivery: Events are delivered on a best-effort basis. There might be a slight delay in event delivery or processing.
-
Activity Level: If there haven't been any successful logins from Windows clients to your WorkSpaces, you won't see any events.
To troubleshoot:
- Double-check that you have active WorkSpaces and that users are logging in from Windows clients.
- Verify that your rule is in the correct region.
- Check the CloudWatch Logs resource-based policy to ensure EventBridge has write permissions.
- Consider broadening your rule pattern temporarily (e.g., remove the "detail" section) to see if you're receiving any WorkSpaces events at all.
If you've verified all these points and are still not seeing events, you may want to contact AWS support for further assistance.
Sources
Amazon WorkSpaces events - Amazon EventBridge
Using resource-based policies for Amazon EventBridge - Amazon EventBridge
Monitor WorkSpaces Personal - Amazon WorkSpaces
Relevant content
- asked 9 months ago
- asked 2 years ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 2 months ago
All these troubleshooting methods are not working.