When creating an FSx windows fileshare is this cod...
# general
When creating an FSx windows fileshare is this code expected? https://github.com/pulumi/pulumi-aws/blob/12e670b7058a95d189b26e09a2864e3d7c210466/sdk/nodejs/fsx/windowsFileSystem.ts#L343 Currently it's:
Copy code
     * A list of IDs for the subnets that the file system will be accessible from. File systems support only one subnet. The file server is also launched in that subnet's Availability Zone.
    readonly subnetIds: pulumi.Input<string>;
Shouldn't the type be
As noted in the comment, it looks like this property (currently?) only supports one item. It is not clear why it is plural - it may be that in the future it is expected to expand to accept a
as well?
I'm not familiar enough with FSx, but I do have hosts spread across multiple subnets. Can I give any subnet in Pulumi and then reconfigure it via AWS console later?
From https://aws.amazon.com/fsx/windows/faqs/:
Q: How do I deploy multi-AZ file systems with Amazon FSx?
A: For workloads that require multi-AZ redundancy to tolerate temporary AZ unavailability, you can create multiple file systems in separate AZs, keep them in sync, and configure failover between them, using Amazon FSx for Windows File Server’s support for Microsoft’s Distributed File System (DFS) Replication and Namespace features. DFS Replication allows you to automatically replicate data between two file systems, and DFS Namespace allows you to configure automatic failover.
ah... okay
Though to your specific question - you should have no problem reaching the FileSystem from hosts in other AZs - you'll just have a slight SPOF AZ issue because it appears FSx is a zonal not regional service.