Questions tagged with Amazon FSx for Windows File Server
Content language: English
Sort by most recent
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  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.  - 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.
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