amazon ec2network-sharewindows
I have a number of Windows servers in EC2 on the same VPC. How can I get those machines to share folders with each other?
The closest answer I see is here: Unable to Share Data between Amazon EC2 Instances for Windows
But it's a pretty old post and I cannot get it to work by simply enabling TCP and UDP on ports 135-139 and 445.
I want to be able to say \\server1\shared_folder from my server2 machine.
I found the answer to my own query, and here it is:
Theory:
This can be found at this Microsoft knowledgebase article which deals with the ways to enable Microsoft file sharing SMB. The below matter is of relevance:
The following ports are associated with file sharing and server message block (SMB) communications:
- Microsoft file sharing SMB: User Datagram Protocol (UDP) ports from 135 through 139 and Transmission Control Protocol (TCP) ports from 135 through 139.
- Direct-hosted SMB traffic without a network basic input/output system (NetBIOS): port 445 (TCP and UPD).
How to do it:
Enable the above ports in the security group associated with your EC2 Instance. Once you have done this, your Security Group Permissions should look something like the image below:
Enable the ports in the windows firewalls of both the instances. A detailed method to do so can be found here. Skip step 7 for Windows Server.
This solves the issue, however, a restart of the instances might be needed.
So, if I share a folder on the DC (Server1) and set the permissions to allow full access for "Everyone", I cannot copy files onto this share from my Windows 7 Workgroup computer
Judging by your comments, it seems that you've only set the NTFS permissions, but probably are using the default Sharing permissions, which are read-only. What you need to do is go into the Share Properties for that share and set the appropriate permissions. It's located in the Sharing tab, next to Security in the Properties window.
Generally, I grant Everyone Full Control in the share permissions and control access through NTFS ACLs. It's much easier to manage that way.
Best Answer
You can simply create a security group and then add an inbound rule to allow all traffic from it's own security group and then add these security group in both instances to share data with each other but there's an better approach for this is to use FSx in AWS.