Questions tagged with Amazon FSx for Windows File Server

We are interested to use AWS FSx for Windows plus install FSx File Gateway at our main site. There will be multiple users using the File System, some from within the site and others will be accessing FSx directly from the internet. Our concern is whether a change made from a user on-site will be synchronized immediately and be visible to other users, or if there is a delay. What is the minimum time does the FSx Gateway send its changes to the main AWS FSx? Is it near real-time, or more (like minutes)? Does a "write" stay on the FSx Gateway cache for a while or is it written immediately to the FSx? Thanks in advance.

I am trying to extend the retention of already made backups in FSx for Windows. AWS Backup can have unlimited retention but in the console for FSx you can only do a maximum of 90 days. For existing backups can they be copied and then categorized as a user-initiated backup and then use the Custom Backup schedule [1] extend the retention based on whats defined? Importing the Automatic backups defined in the FSx console would be ideal but I have not found a way to do this. [1] - https://docs.aws.amazon.com/fsx/latest/WindowsGuide/additional-info.html

Is it possible for us to mount an AWS FSx for Windows File Server file share onto our ECS EC2 host? Today, we have an application hosted on a Linux server with those FSx file shares mounted directly. Now that we are attempting to containerize these applications, we've come across this potential roadblock. Is this possible with ECS on EC2? Or, better yet, is this possible with ECS on Fargate? Thank you!

I have stood up FSx for windows and I can connect to the shares and manage them fine. I have include the necessary ports in the SG to manage the service from the documentation. However, when I tried to connect via WinRM on port 5985 to the FSx instance, it fails to connect. I can connect via SMB 445 when running a test and we confirmed that by connecting to the service and creating shares. SMB and WinRM are opened in the same SG for FSx, so it makes no sense. All ports are allowed outbound and the NACL is still set to default all open in both directions. What is even more strange is that a connectivity analysis test says the port is open between the same instance and ENI for FSx (445 and 5985), but from inside the instance it is not open when doing a test. Local firewall is disabled and all ports open on instance SG and NACL for the same local private subnet (FSx and instance). This is very bizarre. Anyone else run into this? https://docs.aws.amazon.com/fsx/latest/WindowsGuide/self-manage-prereqs.html

Hello, our customer has multiple on-premises sites and would like to connect them all to use one AWS FSx for Windows File Server. Can we install FSX Storage Gateways on each of the sites, then connect them all to the same FSx on AWS? Will this have any problems with file ownsership, locking, etc.? Thanks in advance. H. Baligh

We want to create a 2-way replication between AWS FSx and an on-premise Windows file server. Can we do this using AWS DataSync or DFS Replication? The purpose is to use AWS FSx as active-active DR solution for an on-premises Windows file server. From what I found so far, AWS DataSync does not support bi-directional replication. As for DFS Replication, it does not support file locking so multiple people can't work on the same files simultaneously.

Can we create life Cycle Rule for FSx Windows File System? any docs

Hi, i am evaluating fsx for windows file server. I can not understand, is it a pay-as-you-go service or not? In other words, if I provision a 1TB storage, when it is full, will uploads stop or will I be billed accordingly at the end of the month? Thanks in advance.

I want to create a folder in the shared top directory of FSx. Flow Powershell commands using ssm's AWS-RunPowerShellScript. However, the executing user is ssm-user. This user is not an active directory user and access is denied. The New-Item command does not set credentials. Is it possible to create a folder in the FSx shared top directory by running the powershell command from ssm?

Does FSx for Windows File Server support 0 byte files, files without extension and long file path names(beyond normal Windows Desktop OS limits)?

1.Is there any way that we auto assign tag to FSx backups? 2.What is file archival option in AWS FSx for windows file system?

Besides using the SMBLibrary, is there any way to access a windows FSx filesystem from a lambda function written in C#? Is there a way to mount the FSx filesystem in the lambda so it can be used?

Trying to understand the role a CMK can play in protecting data. Obviously one layer of protection is the ACLs we use to lock down folders on our FSx share by allowing only certain AD users/groups read, write permissions etc. What role does the CMK key play? Can a policy on that key for that file system add a second layer, disallowing some AD users (federated roles) to decrypt etc. ? My initial testing with a CMK key policy on an FSx file system doesn't seem to bear this out. Hope my question makes sense. Thanks

In testing deduplication enablement, it appears that by disabling deduplication, it leaves existing deduplication in state (forever). Would like to be able to completely disable and re-inflate data if performance issues encountered due to deduplication enablement. -- Re: existing ticket XXXXXXXXXX *Edit: Removed case ID — John M.

I have an ECS service which is of Launch Type EC2 owned by an AWS account A. Our IT team has created an FSx storage owned by an AWS Account B - [see simple diagram here](https://i.stack.imgur.com/MyU1d.png) When I try to launch tasks I get this error in the Stopped reason section of the task: ``` Stopped reason Fsx describing filesystem(s) from the service for [fs-0c52aba0aac20c744]: FileSystemNotFound: File system 'fs-0c52aba0aac20c744' does not exist. ``` I have attached those 2 policies to the EC2 (container host) instance: - AmazonFSxReadOnlyAccess (AWS Managed) - fsx_mount (Customer Managed) fsx_mount: ``` { "Statement": [ { "Action": [ "secretsmanager:GetSecretValue" ], "Effect": "Allow", "Resource": "arn:aws:secretsmanager:us-west-2:111111111111:secret:dev/rushmore/ad-account-NKOkyh" }, { "Action": [ "fsx:*", "ds:DescribeDirectories" ], "Effect": "Allow", "Resource": "arn:aws:fsx:us-west-2:222222222222:file-system/fs-0c52aba0aac20c744" } ], "Version": "2012-10-17" } ``` **Note** that the account id of 222222222222 represents AWS Account B. Also, **VPC Peering is in place between the EC2 instance VPC and the FileSystem VPC**. Terraform aws_ecs_task_definition: ``` resource "aws_ecs_task_definition" "participants_task" { volume { name = "FSxStorage" fsx_windows_file_server_volume_configuration { file_system_id = "fs-0c52aba0aac20c744" root_directory = "\\data" authorization_config { credentials_parameter = aws_secretsmanager_secret_version.fsx_account_secret.arn domain = var.domain } } } ... } ``` I am not sure why ECS cannot find the FSx file system. Surely it must be because it is in another AWS account but I don't know what changes are required in order to fix this.

Is it possible to recover individual file or folder from FSX file system.

My container is configured to mount an FSx volume, which succeeds on first run. But... each time the task runs and the container exits, it leaves in place the SMB mapping on the EC2 instance: PS C:\Windows\system32> gdr -PSProvider 'FileSystem' Name Used (GB) Free (GB) Provider Root CurrentLocation ---- --------- --------- -------- ---- --------------- C 33.87 66.12 FileSystem C:\ Windows\system32 D 0.09 31.91 FileSystem \\amznfsxka9h1c5.... E 0.09 31.91 FileSystem \\amznfsxka9h1c5.... F 0.09 31.91 FileSystem \\amznfsxka9h1c5.... G 0.09 31.91 FileSystem \\amznfsxka9h1c5.... H 0.09 31.91 FileSystem \\amznfsxka9h1c5.... . . . Z 0.09 31.91 FileSystem \\amznfsxka9h1c5.... PS C:\Windows\system32> Eventually the instance runs out of drive letters, leading to this: STOPPED (Could not find an available drive letter to mount fsxwindowsfileserver resource on the container instance) Is there some cleanup I should be doing to ensure the container doesn't leave behind these drive letters?

Hi there, I managed to add FSx for NetApp ONTAP to our domain with FSxServiceAccount as described on the product page. However, I am running into issues when I am trying to attach it to my Windows instance. (It works fine on Linux). I see the following issues: - When I am running this command New-SmbGlobalMapping -Persistent $true -RemotePath \\<IO of my smb>\share -Credential $creds -LocalPath G:` I get the following error: `New-SmbGlobalMapping : Access is denied.` - I am using domain admin credentials - When I am running this command `net use Z: \\<dns address of the smb>\share` I got the following error: `System error 5 has occurred. Access is denied.` - Also with domain admin creds - I can successfully attach via File Explorer > This PC > Computer >Map network drive, however I can not read/write to it. If I check the FIle permission mode in Propertires I can see that only the owner (FSxServiceAccount?) is allowed to write, however Read should work, but I can not change the permissions as domain Admin. I am using Directory Service Standard Edition. Did you guys experience issues with this? What am I doing wrong? **Update:** I managed to attach the disk, but I can not write or read any file on the disk. It is in OU=Computers, and allowed Everyone Full Access, also allowed Everyone Read/Write the NFS filesystems attached to the AD, but still not working. I am suspecting this is something NetApp specific, but we will see. **Update #2** Based on CloudWreck's comment I found the following: I am using mixed style. I use the following code: ``` net use P: \\WINDOWS\vol1 $CurTgt = "P:" $CurUsr = [System.Security.Principal.WindowsIdentity]::GetCurrent().Name $acl = Get-Acl $CurTgt $AccessRule = New-Object System.Security.AccessControl.FileSystemAccessRule($CurUsr,"FullControl","ContainerInherit,ObjectInherit","None","Allow") $acl.SetAccessRule($AccessRule) $acl | Set-Acl $CurTgt ``` Get-Acl returns ``` Path Owner Access ---- ----- ------ P:\ Everyone Everyone Allow -1 ``` Also using this one: ``` $CurTgt = "P:" $CurUsr = [System.Security.Principal.WindowsIdentity]::GetCurrent().Name $acl = Get-Acl $CurTgt $usersid = New-Object System.Security.Principal.Ntaccount ($CurUsr) $acl.PurgeAccessRules($usersid) $acl | Set-Acl $CurTgt ``` Also tried this: ``` takeown /F * /R takeown : ERROR: File ownership cannot be applied on insecure file systems; ``` But I am still unable to write/read files or create folders. **Update#3** I ran the following commands and changed the permission from the ONTAP side ``` vserver security file-directory show -vserver windows -path /vol1 vserver security file-directory ntfs create -ntfs-sd sd1 -owner DomainName\Administrator vserver security file-directory ntfs sacl add -ntfs-sd sd1 -access-type success -account DomainName.COM\EVERYONE -rights full-control -apply-to this-folder,sub-folders,files vserver security file-directory ntfs dacl add -ntfs-sd sd1 -access-type allow -account DomainName.COM\EVERYONE -rights full-control -apply-to this-folder,sub-folders,files vserver security file-directory policy create -policy-name policy1 vserver security file-directory policy task add -policy-name policy1 -path /vol1 -ntfs-sd sd1 vserver security file-directory apply -policy-name policy1 vserver security file-directory show -path /vol1 -expand-mask true ``` It changed the file permissions (mode), however I am still unable to read/write files. These are the current settings: ``` File Path: /vol1 File Inode Number: 64 Security Style: mixed Effective Style: ntfs DOS Attributes: 10 DOS Attributes in Text: ----D--- Expanded Dos Attributes: 0x10 ...0 .... .... .... = Offline .... ..0. .... .... = Sparse .... .... 0... .... = Normal .... .... ..0. .... = Archive .... .... ...1 .... = Directory .... .... .... .0.. = System .... .... .... ..0. = Hidden .... .... .... ...0 = Read Only UNIX User Id: 0 UNIX Group Id: 0 UNIX Mode Bits: 777 UNIX Mode Bits in Text: rwxrwxrwx ACLs: NTFS Security Descriptor ``` ``` ALLOW-Everyone-0x1f01ff-OI|CI 0... .... .... .... .... .... .... .... = Generic Read .0.. .... .... .... .... .... .... .... = Generic Write ..0. .... .... .... .... .... .... .... = Generic Execute ...0 .... .... .... .... .... .... .... = Generic All .... ...0 .... .... .... .... .... .... = System Security .... .... ...1 .... .... .... .... .... = Synchronize .... .... .... 1... .... .... .... .... = Write Owner .... .... .... .1.. .... .... .... .... = Write DAC .... .... .... ..1. .... .... .... .... = Read Control .... .... .... ...1 .... .... .... .... = Delete .... .... .... .... .... ...1 .... .... = Write Attributes .... .... .... .... .... .... 1... .... = Read Attributes .... .... .... .... .... .... .1.. .... = Delete Child .... .... .... .... .... .... ..1. .... = Execute .... .... .... .... .... .... ...1 .... = Write EA .... .... .... .... .... .... .... 1... = Read EA .... .... .... .... .... .... .... .1.. = Append .... .... .... .... .... .... .... ..1. = Write .... .... .... .... .... .... .... ...1 = Read ```

Hi there, When I am trying to join my domain (using Directory service), I am receiving the following error: ``` Amazon FSx is unable to establish a connection with your Active Directory domain controller(s) because the service account credentials provided are invalid. To fix this problem, delete your storage virtual machine and create a new one using a valid service account as recommended in the Amazon FSx user guide. ``` I have read the user guide, and followed all the steps. Now, I am using the same security group as the domain controller and allowing all traffic inside the sg. I checked with Reachability analyzer, the ENI from fsx can communicate with the domain controller's domain controller. I also tried to use the domain admin, just to make sure - but for some reason it does not work. Did any of you experienced something similar?

Hello, Is normal that FSX allocates a new IP always data sync run? I've been checking and most of these IPs are 'available'.

Setting aside single-AZ vs multi-AZ, we offer [two different pricing tiers][1] for FSx, those being with and without data deduplication. Looking at storage costs, the pricing with deduplication enabled is half that of non-deduped FSx with the assumption of a typical 50% deduplication rate. We've also documented that deduplication is transparent to the end user and [doesn't significantly affect the file system's performance][2]. With that said, are there any potential reasons customers should not enable deduplication? [1]: https://aws.amazon.com/fsx/windows/pricing/ [2]: https://docs.aws.amazon.com/fsx/latest/WindowsGuide/using-data-dedup.html

A customer has deployed an Amazon FSx for Windows File Server joined to his self-managed Active Directory. He noticed that Amazon FSx is creating 4 different computer objects into its OU for 1 file system, 4 new computer objects for another file system, etc. which will result in a very difficult situation to manage those file systems at scale. [Nothing in particular is mentioned within our documentation except to not move computer objects that Amazon FSx creates in the OU after your file system is created][1] Is it the normal behavior of Amazon FSx for Windows File Server with self-managed AD? Do you have any clue which may help to better understand Amazon FSx behavior? Thank you very much in advance for your feedback [1]: https://docs.aws.amazon.com/fsx/latest/WindowsGuide/self-managed-AD-best-practices.html

Hi, I am trying to increase an FSx for Windows Storage Capacity from 3TB to 4TB. I increased it yesterday from 2TB to 3TB and it worked fine. Today, when I try to do it, it gives me this message: Unable to perform the storage capacity update; there is a request already in progress. But the increase from yesterday finished, so why can't I increase it today? Thanks. Paul

I've created an FSx file system but I can't seem to access it via a cname. I can access it fine via the DNS name from Amazon. However, when I create the cname record if I browse to the root \[cname]\ it comes back with "This folder is empty." If I include a share name like \[cname]\IT it gives me a hard failure telling me, "windows cannot access \[fileshare]". The storage type is SSD and single-AZ 2. Any suggestions or additional information needed?

A customer is interested in accessing FSx for Windows from remote clients and their office network without using VPN since they only have a few users and are not storing sensitive data. * Is it possible to expose FSx over public internet? It seems that FSx only gets assigned a private IP. * Are there any workarounds that can be done that will be cheaper than running VPN? Thank You!

A customer is exploring the FSx HDD option. While looking at the cost of backup of FSx(https://aws.amazon.com/fsx/windows/pricing/), it seems the backup cost is higher then the actual storage cost. Like for single Az deployment , HDD storage capacity cost is 0.013per GB-month, while backup is 0.050 per GB-month, Is there any specific reason? Is it due to the fact that backup is going to be stored in S3?

A customer has files on S3 (provided by Transfer Family) and they need to copy/move files uploaded to S3 to their FSx for Windows. This could be done with a dedicated machine to do this job. However, I wonder whether it is possible to solve this without the need to manage a dedicated EC2 instance. My best guess so far is to use DataSync. I know that I can't use the combination "Location S3, destination FSx". However, the combination "Location S3, destination SMB" is possible. 1) Is it possible to use DataSync for the combination "Location S3, destination SMB (and this is actually FSx)"? 2) Are there any pitfalls to solve the customer's problem in this way? 3) Do you see a better solution to move files from S3 to FSx?

I'm trying to use Amazon FSx for SAP on Windows High Availability environment, but run into an issue where I can’t assign a CNAME to Amazon FSx Multi-AZ file system deployment. (CNAME works fine in Single-AZ file system deployment) I also can’t use the native AWS naming of the Amazon FSx file system ID as this is more than 13 chars, which is not supported by SAP. Are you able to provide some guidance around how we set up the SAP Central Services to use Amazon FSx Multi-AZ file system for our SAPGlobalHost share ? (Have seen some documents that loosely implies you need to setup DFS replication between 2 Single-AZ file system deployments, is this correct as it seems very clunky and not a straight forward solution?)

Customer would like to know the IOPS performance when the volume is <1TiB. From doc ( https://docs.aws.amazon.com/fsx/latest/WindowsGuide/performance.html ), it stated 3,000 Disk IOPS per TiB of storage, what if customer provisioned 500GiB volumes, will it be 3,000/1,500 IOPS? (Shall we consider 3 IOPS per GiB?)

For SQL Server running on EC2 and using FSx, when the FSx maintenance window happens, will there be an interruption to SQL Server ? Do the databases become disconnected?

Hi, I can't deploy FSx in my application account because it doesn't like AD Connector. I've tried deploying FSx in my shared services account but, although DNS resolves, mapping a drive results in "resource ... is not responding". The default security group limits outgoing traffic to itself. Should I add another rule for my application account's VPC? Thanks, TL

Hello Currently, 100TB of data is compressed to 50TB using the deduplication function of Windows.(EC2 on AWS) I want to migrate this data to FSx for windows. (The FSx pricing structure costs because of storage and throughput capacity) ec2⇒robocopy⇒FSx for windows However, if you remove the deduplication function when performing data migration, the data capacity will return to 100 TB and a lot of costs will be incurred. Is there a specific way to migrate data to FSx with the data deduplicated? We want to reduce the cost and migrate data to FSx. I want to use windows robocopy as the data migration method.

Hello, We have really been looking forward to the HDD storage-type and now with it being launched we want to try this out and migrate to FSx from our legacy fileshares. However when reading the CF-documentation here: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-fsx-filesystem.html I can see it mentions: ``` For Windows file systems: If StorageType=SSD, valid values are 32 GiB - 65,536 GiB (64 TiB). If StorageType=HDD, valid values are 2000 GiB - 65,536 GiB (64 TiB). ``` however neither in "AWS::FSx::FileSystem" or in "AWS::FSx::FileSystem WindowsConfiguration" I can find where to specify that parameter to set the FSx resource to the HDD storage-type. A blocker for us to launch FSx using the HDD-option, would appreciate assistance / how and where to specify storagetype to HDD. Best Regards - TheSwede86 **Update 2020-04-02**: Heard it was going to be fixed / added soon so I'm closing this.

Hello, a customer has 30TB of Windows shares and would like to have a DR solution for it in AWS. I thought first about using FSx for Windows and using DataSync to continuously import data from on-prem to FSx. However I would like to decrease the price of the solution: is it possible to have this kind of flow? 1. First import the data from on-prem to S3 2. Store the data in S3 when the DR is not activated 3. Make incremental backups regularly to S3 4. Finally, import to FSx when the DR is activated ? The customer is also using CommVault as a third-party tool. Thank you in advance.

Hello everyone , Instead of finding the solution for my last post i thought it would be better to ask . I have this enveironment : - one Load Balancer with a target group of 2 windowss EC2 instances running a web app on port 80 - both windowss ec2 must have a shared drive eg: an " D:\ " What would be the best aproach for this situation ? I already created this env. but i cannot succed in creating the shared drive. What i have tried : 1. an FSX share but after i joined the windows ec2 instances the tomcat service cannot see that drive. I have tried to run the tomcat service either with the Local System user(default) or the Domain User that is an local Admin and also with the Local Workgroup Adminstrator. Here i have also tried with MKLINK and same outcome. 2. I thought in creating a FailOverCluster between the nodes and then add a storadge and create a Cluster Shared Volume. This might work but i think its an "overkill" as infrustructure and also prices. (even thou im not sure what type of storage to add to the ec2 instances , in phisical env. this would require a SAN with ISCSI). So , please let me know if there are other solution i should take in consideration. Thank you for reading my post.

We are currently migrating to AWS and have around 90 TB of CIFS/SMB shares to be migrated to AWS and we are thinking of using FSX. However, there is a requirement within the applications to use the same share name as on prem. Can this be achieved by FSx for Windows? Example: On prem application reads/writes to a share - \\nanpfssvfp01a\VMS_Entapps_1\Active_X Is it possible to retain the same naming convention on FSx? Example: The application reads and writes to share "\\nanpfssvfp01a\VMS_Entapps_1\Active_X". Can this be share name be retained?

Hello, I have been stuck on trying to mount FSx on ec2 instances and workspaces. Both are joined in the AWS managed active directory. The security group associated with FSx is the default wide open one. I've attempted this as the domain admin but always get network path not found. Any help would be greatly appreciated. Thank you.

Does AWS scan the FSx filesystem for malware? If not, what is the recommended method of scanning the FSx filesystem for malware files uploaded to the shares? Should we map a drive to the fsx file system from a windows server and then scan the drive? Any other ways to do this? Thanks.

I am attempting to use the recommended cloud formation template to create a custom backup schedule for fsx. I am following the documentation to use the recommended cloud formation template using these steps: https://docs.aws.amazon.com/fsx/latest/WindowsGuide/custom-backup-schedule.html The template if failing to create with error: The following resource(s) failed to create: \[BackupManager]. . Rollback requested by user. 16:36:59 UTC-0500 CREATE_FAILED AWS::Lambda::Function BackupManager Error occurred while GetObject. S3 Error Code: PermanentRedirect. S3 Error Message: The bucket is in this region: us-east-1. Please use this region to retry the request (Service: AWSLambdaInternal; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: 4ddde0bd-41ea-11e9-81a0-9ff5109c54de) Looks like it is failing because the cloud formation template is in us-east-2 but it is attempting to access a bucket in east-1. How do I fix this? I do not see any settings in the cloud formation template to change the bucket to us-east-2. Anyone have any advice?

Hello, I was wondering if anyone could provide some guidance. I've got a share built in us-east-1. There is a trust between my on prem domain and the managed ad fsx is joined to. The "Everyone" group and my specific user account from the on prem domain have full permissions on the share. According to this post, it seems the share should be accessible via VPN: https://aws.amazon.com/about-aws/whats-new/2019/02/amazon-fsx-for-windows-file-server-now-supports-on-premises-access/ However, when I attempt to connect to the share from an on prem machine in the trusted domain with my user account, I receive the following error message "windows cannot access \\filesystemid.managedad.com\share Check the spelling of the name. Otherwise there might be a problem with your network..." There's no issue with network connectivity, VPN is up, routes are there, SGs are allow all from the on prem subnet, NACLs are allow all inbound and outbound, host based firewalls are off and network based firewalls are allow all outbound, I can resolve host names in the managed ad via my on prem forwarder (including the IP of the filesystem), I can ping and rdp into stuff in the same subnet, heck even my VPC flow logs for the FSX network interface show Accepts from my on prem host to the fsx eni on ports 445, 139, and 120. Despite all this, I get the above error when attempting to use the share, and I cannot telnet to the IP of the share on port 445 from my on prem machine. Telnet to the same port and IP from within the subnet works. Again, there is nothing but Accepts in my flow logs. It seems like it has to be fsx dropping the traffic? What am I missing? Any help would be greatly appreciated.

On February 14, 2019 it was reported that FSx provides support for CloudFormation but I can not find the resource in the cloud formation designer. I tried it with the following regions : Northern Virginia, Ohio and Oregon. If someone could find the resource, I will really appreciate your help.

Hi guys we are using FSX from some week and we feel the lack of a monitor where we can see how much Throughput we are using at the moment(such as dynamoDB metrics charts) and based on this the ability to scale it up . Thanks for the answers.

On the following thread, it says that AWS Directory Service (Microsoft AD) can be used for DFS Replication. https://forums.aws.amazon.com/thread.jspa?threadID=244580 Nowhere in the documentation does this get mentioned for FSx. Can we use it for FSx, or must be have a Windows server for this purpose? Thanks, Paul.

Hello, Our company is looking to move our environment to AWS GovCloud this year and I'm working on verifying that all the features and configurations will work when we move. Currently we use DFS to sync files between Windows servers but I'd like to evaluate FSx to replace DFS. When will you have FSx available in GovCloud? How about N. California? I will use Oregon to do the evaluation and tests but we are located in California and would like to see our environment closer to us. Thanks.

How do I access Freespace/usedspace/totalspace stats on my FSx filesystem? I do not see a way to do this with the console or powershell.