Enabling Windows EC2 clients to access NFS volumes
J
Jjbegin
started a topic
over 11 years ago
Setting up the Windows installation media
Amazon's Windows EC2 AMIs do not include the installation media as part of the base OS install. Since we obviously can't insert a Windows CD when prompted, we have to attach an EBS volume to the instance containing the Windows files.
Identify the correct EBS snapshot. Depending on your OS version, CPU architecture, and region.
Create a volume from the snapshot. Ensure that the volume is located in the same availability zone as your EC2 instance
Attach volume to EC2 instance
Installing the Windows NFS client
Go to Control Panel --> Add or Remove Programs
Click "Add/Remove Windows Components" on the left sidebar
Highlight (but don't tick the checkbox) "Other Network File and Print Services"
Click the "Details" button
Select "Microsoft Services for NFS" and click "Details"
Tick the boxes for "Client for NFS" and "User Name Mapping"
Click the Ok and then the Next buttons
When prompted to browse to the file location find E:\Disc2\CMPNENTS\R2 and click the Ok button.
Click the Finish button
Configuring User Name Mapping
NFS uses UNIX user IDs (UIDs) and group IDs (GIDs) to determine file ownership and permissions. UID/GIDs are simply numeric representations of user and group names. For example the root user most commonly has a UID of "0." The User Name Mapping service under Windows provides a means to translate Windows user names/UUIDs to a matching UNIX UID.
Copy the "/etc/passwd" and "/etc/group" files from the NFS server or a spare a Linux server to the Windows server. Optionally, these files can be copied directly to the NFS volume so that all clients can easily access the file. (Despite it's name, the "passwd" file does not contain passwords and it is minimally risky to share access.)
Jjbegin
Setting up the Windows installation media
Amazon's Windows EC2 AMIs do not include the installation media as part of the base OS install. Since we obviously can't insert a Windows CD when prompted, we have to attach an EBS volume to the instance containing the Windows files.
Identify the correct EBS snapshot. Depending on your OS version, CPU architecture, and region.
Create a volume from the snapshot. Ensure that the volume is located in the same availability zone as your EC2 instance
Installing the Windows NFS client
E:\Disc2\CMPNENTS\R2
and click the Ok button.Configuring User Name Mapping
NFS uses UNIX user IDs (UIDs) and group IDs (GIDs) to determine file ownership and permissions. UID/GIDs are simply numeric representations of user and group names. For example the root user most commonly has a UID of "0." The User Name Mapping service under Windows provides a means to translate Windows user names/UUIDs to a matching UNIX UID.
Copy the "/etc/passwd" and "/etc/group" files from the NFS server or a spare a Linux server to the Windows server. Optionally, these files can be copied directly to the NFS volume so that all clients can easily access the file. (Despite it's name, the "passwd" file does not contain passwords and it is minimally risky to share access.)
Click "List Windows Users." The Windows users list should populate.
Click "List UNIX Users." After 15-20 seconds, the UNIX users list should populate.
Either reboot the server. (Restarting the "Client for NFS" service itself may or may not be enough.)