Docs

    AWS File Server (FSx)

    AWS FSx is a fully managed service that allows you to launch, run, and scale file storage for use with compute and container services. While it simplifies file storage management, issues such as misconfigurations, network problems, or performance degradation may arise during operation. This guide outlines common errors and provides troubleshooting steps specific to FSx for Windows File Server.

     

    We monitor the following metrics:

    • aws.file_system_cpu.percent
    • aws.file_system_storage.percent
    • aws.file_server_disk_throughput.percent
    • aws.file_system_memory.percent
    • aws.file_server_disk_iops.percent

     

    We continuously monitor these metrics on your AWS Windows file systems, creating Events whenever thresholds are exceeded or significant changes occur. 

     

    Common Errors When Monitoring AWS FSx for Windows File Server

    When monitoring AWS FSx for Windows File Server, several issues may arise that affect the performance, availability, and integration with your environment. Below are common errors and their potential resolutions.

     

    IAM Role Permissions Issues

    Possible Causes

    • Missing Permissions
      • Ensure that the IAM role assigned to FSx has the necessary permissions to interact with VPC resources, security groups, and the FSx API.
      • Check that the role has access to other services, such as S3, if needed for backup or integration.
    • Incorrect Role Assignment
      • Verify that the correct IAM role is associated with your FSx file system during the setup process.

     

    Exceeding Storage Capacity

    Possible Causes

    • File System Reaching Capacity
      • Monitor the storage capacity of your FSx file system to ensure it doesn't run out of space.
      • Enable automatic storage scaling if available, or manually increase the storage capacity through the AWS Management Console.

     

    Active Directory (AD) Integration Failures

    Possible Causes

    • Incorrect AD Credentials or Permissions
      • Ensure that the AD service account has the necessary permissions to join the FSx file system to the domain.
      • Confirm that the correct domain credentials are supplied during FSx setup.
    • Network Connectivity Issues with AD
      • Verify that the FSx file system can reach the domain controllers over the network.
      • Check your DNS configuration to ensure domain controller resolution is functioning properly.

     

    File System Performance Degradation

    Possible Causes

    • Excessive SMB Connections
      • Monitor the number of concurrent SMB connections. If too many users or services are connected simultaneously, it can lead to performance bottlenecks.
      • Consider distributing workloads or increasing the size of the file system to handle more connections.
    • Throughput Capacity Limit Reached
      • Check if your file system has reached its throughput capacity. Increase the throughput capacity if necessary by adjusting the file system's size or switching to a higher-performance tier.
    • Burst Credit Depletion
      • FSx for Windows File Server uses burst credits for performance boosts. If the credits are depleted, the file system will return to baseline performance. Monitor burst credit usage through CloudWatch and adjust workloads accordingly.

    By following these troubleshooting steps and regularly monitoring your AWS FSx for Windows File Server environment, you can resolve common issues and optimize performance, ensuring reliable file storage and seamless integration with your network and Active Directory. 


    Resources