FSx for Windows File Server provides SMB shares, directory-based access control, and options for file recovery and failover.
FSx for Windows File Server basics
Amazon FSx for Windows File Server gives Windows workloads managed file sharesA folder and its subfolders made accessible to clients over SMB..
How it works
- Create the file system.
- Windows clients connect to the shares.
- AWS manages the Windows file servers.
Exam cues
- If the question says Windows file shares on AWS, think FSx for Windows File Server.
Remember
- Native Windows file system.
Trap: Linux shared files use Amazon EFS; Windows shares use FSx for Windows File Server.
Da documentação da AWS (3)
- Amazon FSx for Windows File Server provides fully managed Microsoft Windows file servers on a native Windows file system.
- FSx for Windows File Server provides managed Windows file servers and supports SMB versions 2.0 through 3.1.1.
- FSx for Windows File Server joins an AWS Managed Microsoft AD or self-managed Microsoft Active Directory domain for authentication and access control.
SMB, directory integration, and availability
Amazon FSx for Windows File Server provides managed Windows file servers for shared files. Clients use Server Message BlockA protocol for accessing shared files over a network. (SMB), a network file-sharing protocol, and Microsoft Active DirectoryA Microsoft directory service that stores network resources and user accounts. identifies users.
How it works
- Create a file system and join it to AWS Managed Microsoft AD or a self-managed Microsoft Active Directory domain, a directory of users and network resources.
- Expose a file shareA folder and its subfolders made accessible to clients over SMB., a folder and its subfolders, to SMB clients. Users authenticate with directory identities; Windows access control listsA list of permissions controlling access to files and folders., which list permissions, control file and folder access.
- Choose Single-AZ for one file server in one Availability Zone, or Multi-AZ for synchronous replication and automatic failover to a standby in another zone.
- Enable and schedule shadow copiesA point-in-time snapshot of a Windows file system., point-in-time snapshots that let users recover files. Keep backups as well: automatic daily backups are enabled by default.
- To present shares from several file systems under one folder structure, use Distributed File System (DFS) Namespaces.
Exam cues
- If the question says Windows shares and existing domain accounts, think FSx for Windows File Server joined to Active Directory, because it supports SMB and directory authentication.
- If the question says survive an Availability Zone disruption, think Multi-AZ, because it replicates to and fails over to a standby in another zone.
- If the question says users need earlier file versions, think shadow copies, because users can restore files from them once enabled.
- If the question says multiple file systems need one shared folder structure, think DFS NamespacesA Windows Server role service that groups shared folders into a common folder structure., because it groups shares into a common namespace.
- If the question says on-premises SMB access, think Direct Connect or Site-to-Site VPN, because either connects clients to the file system.
Remember
-
File system data and metadata are encrypted at rest using AWS KMS keys.
-
SMB versions 2.0 through 3.1.1 are supported.
-
Multi-AZ failover typically takes less than 30 seconds; failbackThe return of service to the preferred file server after it recovers. is automatic after recovery.
-
Shadow copies are off by default; automatic daily backups are on by default.
-
Windows clients resume using the same DNS name. Linux clients resume after failback, the return to the preferred server, not automatic failover.
Trap: Shadow copies are not a replacement for backups. They are stored alongside file system data.
Trap: Multi-AZ failover is not automatic for Linux clients. They resume access after the preferred server returns.
Windows clients access the file share.
Data is synchronously replicated; FSx fails over to the standby when needed.
Da documentação da AWS (18)
- FSx for Windows File Server provides managed Windows file servers and supports SMB versions 2.0 through 3.1.1.
- FSx for Windows File Server joins an AWS Managed Microsoft AD or self-managed Microsoft Active Directory domain for authentication and access control.
- Windows access control lists control file and folder access; VPC security groups control access at the file system level.
- Single-AZ file systems use one file server in one Availability Zone and recover from component failures.
- Multi-AZ file systems synchronously replicate data across two Availability Zones and automatically fail over to a standby file server.
- Multi-AZ failover typically completes in less than 30 seconds; FSx automatically fails back when the preferred server has recovered.
- Windows applications resume file system operations without manual intervention after failover because the DNS name stays the same.
- Linux clients do not automatically connect to the standby during failover and resume file system operations after failback.
- Shadow copies are point-in-time file system snapshots stored alongside its data that users can use to restore files; they are not enabled by default and do not replace backups.
- Automatic daily backups are enabled by default and manual backups can also be taken.
- DFS Namespaces can group file shares from multiple FSx for Windows File Server file systems under one common namespace.
- A file share is a folder and its subfolders exposed using SMB; the default share is named share.
- On-premises clients can access FSx for Windows File Server shares using AWS Direct Connect or Site-to-Site VPN.
- FSx for Windows File Server supports DFS Namespaces on every deployment type, but DFS Replication only on Single-AZ 1 file systems; Multi-AZ file systems provide their own cross-AZ redundancy.
- FSx for Windows File Server does not support AD Connector or Simple AD; join it to AWS Managed Microsoft AD or a self-managed Active Directory.
- FSx for Windows File Server Data Deduplication lowers storage costs by storing duplicated portions of a dataset only once.
- You can require SMB encryption for the whole file system or for selected file shares, so only clients that support SMB encryption can connect.
- Amazon FSx for Windows File Server automatically encrypts file system data and metadata at rest using keys managed in AWS KMS.
Flashcards
Nada para revisar aqui agora. Escolha outros tópicos ou outro filtro.
·
Todos os 13 flashcards em lista
Windows applications need a shared SMB file system on AWS that works with Windows features. Which service fits?
Amazon FSx for Windows File Server.
Which AWS service fits Windows SMB shares with Active Directory authentication?
FSx for Windows File Server. It supports SMB and joins Microsoft Active Directory.
Windows servers need a shared drive with domain accounts and failover across Availability Zones. Which service and deployment fit?
FSx for Windows File Server with Multi-AZ, joined to AWS Managed Microsoft AD or self-managed Microsoft Active Directory.
An FSx for Windows File Server user needs to recover an earlier version of a file without restoring a backup. What feature helps?
Enable and schedule shadow copies. Users can restore earlier versions from them.
A Windows application needs a managed shared file system with SMB access and Active Directory authentication. Which service fits?
Amazon FSx for Windows File Server provides managed Windows file servers and joins a supported Active Directory domain.
How can multiple FSx for Windows File Server shares appear under one common folder structure?
Use DFS Namespaces to group the shares under a common namespace.
Do Linux clients automatically connect to the standby during FSx for Windows File Server Multi-AZ failover?
No. They resume after failback; Windows clients resume using the unchanged DNS name.
What controls access to individual files in FSx for Windows File Server?
Windows access control lists. Security groups control file system network access.
How can on-premises clients reach FSx for Windows File Server shares?
Use AWS Direct Connect or Site-to-Site VPN.
An on-premises DFS Replication (DFSR) setup keeps files in sync across several Windows servers. What replaces it on AWS?
Amazon FSx for Windows File Server. A Multi-AZ file system gives built-in redundancy across AZs, and DFS Namespaces can group shares; DFS Replication itself is only supported on Single-AZ 1.
A company plans to join FSx for Windows File Server to its on-premises Active Directory through an existing AD Connector. Will that work?
No. FSx for Windows does not support AD Connector or Simple AD. Join it to AWS Managed Microsoft AD or directly to the self-managed AD.
An FSx for Windows File Server share holds many near-identical user files, and storage costs keep growing. Which feature reduces them?
Data Deduplication. It stores duplicated portions of the data only once.
A company chooses Amazon FSx for Windows File Server and requires encryption of stored files. How is encryption at rest provided?
Automatically through AWS KMS keys. FSx encrypts file system data and metadata at rest without application changes.