An Amazon WorkSpaces deployment uses Amazon FSx for Windows File Server as the profile share. The FSx file system is 10 TB and has reached maximum capacity, preventing new sessions. The solutions architect must restore user access and prevent recurrence. Which approach meets these requirements?

The correct approach involves immediately increasing the FSx capacity to restore user access, as FSx for Windows File Server supports online storage scaling. To prevent recurrence, a proactive monitoring and automation solution is essential. Creating a CloudWatch metric for FreeStorageCapacity allows for tracking available space. An EventBridge rule can then detect when this metric crosses a predefined threshold (e.g., storage utilization exceeds 80%) and trigger a Lambda function. This Lambda function can be programmed to automatically execute the update-file-system command to increase the FSx file system's storage capacity, ensuring that the file system does not run out of space again. Deleting old user profiles is a temporary fix and doesn't prevent future capacity issues. Migrating to FSx for Lustre is not suitable for Windows profiles due to protocol incompatibility. Using AWS Step Functions for orchestration is an option, but EventBridge directly triggering Lambda for a single action is simpler and more efficient for this specific use case. Creating an additional FSx file system and redirecting users adds complexity and management overhead compared to scaling the existing file system.