Simple Workgroup

Question

I am new to AWS and need some help.  I am looking for a step by step article if one exist.

I have a simple Workgroup with four computer/workstation and one local file server.  We would like to replace the file server with an AWS EC2 instance as if it was a local server.  From what I understand it looks like we would need the following
A: the EC2 instance with provisioned drivers for files - I can do
B: I guess some type of VPN so that the computers in the office can be connected easily and secure.
C: A security group that would allow the connection
   
On the EC2 instance I would need to install software that allows them to use particular accounting software.
Currently they all have a mapped network drive at each computer where they are storing all their folders and files.  
Your feedback is appreciated.

re:Post Agent · Accepted Answer

You're on the right track with your plan to replace your local file server with an AWS EC2 instance. Here's a step-by-step overview of how you can achieve this:

1. EC2 Instance Setup:
   - Launch a Windows Server EC2 instance. This will act as your file server.
   - Ensure you choose an instance type that meets your performance needs.
   - Attach an Amazon EBS volume to store your files and data.

2. VPN Connection:
   - Set up an AWS Site-to-Site VPN to securely connect your office network to your AWS VPC.
   - This will allow your office computers to access the EC2 instance as if it were on the local network.

3. Security Group:
   - Create a security group for your EC2 instance.
   - Configure it to allow inbound traffic from your office IP range on the necessary ports (e.g., SMB file sharing ports).

4. File Sharing Setup:
   - On your EC2 instance, set up file sharing using Windows File Server roles.
   - Configure shared folders and set appropriate permissions.

5. Software Installation:
   - Install the required accounting software on the EC2 instance.
   - Ensure the software is configured for multi-user access if needed.

6. Client Configuration:
   - Once the VPN is set up, your office computers should be able to access the EC2 instance by its private IP address.
   - Map network drives on each computer to the shared folders on the EC2 instance.

7. Data Migration:
   - Transfer your existing files and folders from the local file server to the EC2 instance.

8. Testing and Verification:
   - Ensure all computers can access the shared drives and run the accounting software.
   - Verify that file permissions are working correctly.

Remember to implement proper backup solutions for your EC2 instance and consider using Amazon FSx for Windows File Server as an alternative to managing your own file server on EC2. It's a fully managed native Windows file system that provides SMB-based access to files.

While there isn't a single comprehensive step-by-step guide for this specific scenario, you can find detailed instructions for each step in the AWS documentation. Be sure to test thoroughly in a non-production environment before making the switch.  
**Sources**  
[EC2 for Windows Server – Amazon Web Services (AWS)](https://aws.amazon.com/windows/products/ec2/)

jayoub · Answer

The AWS Generated answer was great and I think I can use this as my step by step process.

I do have new questions now.
A: Can I set up a VPN from a office that is using Comcast as their ISP and a dynamic IP address
B: Would we need to purchase a static IP Address from Comcast
C: Do you have any idea what the cost of the VPN connection would be
D: What is the cost of the Site to Site VPN for that matter
E: Would users be able to connect to the EC2 from a laptop they took home
F: Would it be easier and less costly if I set up "Workstations/Desktops" in the Cloud for them to use instead of having all the application on there office computers local.

Your feed back is appreciated

Simple Workgroup

Relevant content