Which solution will meet these requirements?
Remove old user profiles to create space. Migrate the user profiles to an Amazon FSx for Lustre file system.
Increase capacity by using the update-file-system command. Implement an Amazon CloudWatch metric that monitors free space. Use Amazon EventBridge to invoke an AWS Lambda function to increase capacity as required.
Monitor the file system by using the FreeStorageCapacity metric in Amazon CloudWatch. Use AWS Step Functions to increase the capacity as required.
Remove old user profiles to create space. Create an additional FSx for Windows File Server file system. Update the user profile redirection for 50% of the users to use the new file system.
Explanations:
Migrating to Amazon FSx for Lustre is not suitable for user profiles as it is optimized for high-performance workloads, not for persistent user data. FSx for Windows File Server is the appropriate solution for Windows-based user profiles.
Increasing capacity using theupdate-file-systemcommand allows for dynamic scaling of the file system. Implementing CloudWatch monitoring and EventBridge to trigger a Lambda function to adjust the capacity automates scaling, preventing the issue from recurring.
While monitoring with the FreeStorageCapacity metric is useful, AWS Step Functions are not ideal for managing automatic scaling of FSx for Windows File Server. The correct approach involves dynamically adjusting capacity using theupdate-file-systemcommand, which is more suited for this use case.
Removing old user profiles creates temporary space, but splitting the user profiles across two FSx for Windows File Servers adds unnecessary complexity. It is better to scale the existing file system instead of managing multiple file systems and handling redirection.
I have a feeling that the answer is:
Increase capacity by using the update-file-system command. Implement an Amazon CloudWatch metric that monitors free space. Use Amazon EventBridge to invoke an AWS Lambda function to increase capacity as required.