2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
1
I would suggest starting with the AWS Pricing Calculator at : https://calculator.aws/#/
You can model both options. If you self-host the Windows File Share you may need to use DFS to provide resiliency across AZs or you can use the native resiliency o FSx.
0
“Thanks, Michael. Is it possible to provision a single FSx across multiple VPCs, or should we have a dedicated FSx per VPC that is accessible by both public and private subnets? On my end, both public and private subnets need to access the file share due to business requirements. Could you please suggest what the ideal FSx design would be for such cases?”
beantwortet vor 5 Monaten
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor 7 Monaten
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
A given FSx for Windows deployment is specific per VPC and the subnets you select in a multi-AZ deployment. However, as long as there is network connectivity between the VPCs, the single FSx for Windows deployment can be accessed across VPCs. If you have something like a "Shared Services" VPC, then I would deploy FSx in that VPC and use it from all other VPCs. You may have a business reason for separating out individual FSx deployments, but it is not a technical requirement.