In one of our client scenario each laptop running a client software has to have a mapped S:\ drive.
Earlier they would map this S:\ drive to a drive in a Server on the same network like \\Server-name\$D
Now they are planning to move this server to EC2 in AWS. Is it possible to map the drive from EC2 server in local machine?
Local machine is in aclient network connected to AWS via VPN and DirectConnect.
In my research online (I am trying to map an Amazon EC2 drive to a local machine), I came to know that you can enable a VPN on EC2 server to make this happen. But I am looking for a inbuilt windows option as this is a as-is migration to AWS.
Related
I've setup an Ec2 instance of Windows server 2016 on AWS.
I can map to a shared drive on this instance from my home (desktop, and laptop) and mobile device. I use domain from home, and IP on mobile.
I bring my laptop to the office and am unable to map to the drive. I have access to RDP still, but no SMB. I believe this is blocked from the ISP.
I tried connecting from home, while connected to a different location on ExpressVPN, and was unable to connect.
The instance hosts software used by the company. There is a DB on the instance and the software on the workstations/endpoints is able to connect to the DB on the instance.
I read I should switch the SMB port to 80. I opened some ports, but still can't connect.
I want to connect an external Wi-Fi adapter from my local PC to a Windows Server in AWS.
Is it possible?
It appears you are wanting to make your local wifi (eg at home or in the office) accessible to an Amazon EC2 Windows instance.
This is not a capability provided by AWS.
You might be able to find a software product that can extend a USB device or a network connection between two computers across the Internet. For example, I have seen people use a virtual serial port to allow a "dongle" to be connected to a virtual computer. However, any such solution is something you would configure in the Windows operating system and your own computer. It would not have anything specific to do with Amazon EC2.
I currently develop a small Java web application with following stack: Java 8, Spring Boot, Hibernate, MariaDB, Docker, AWS (RDS, Fargate, etc.). I use AWS to deploy and to run my application. My java web application runs inside of the docker container, which is managed by AWS Fargate; this web application communicates with Amazon RDS (MariaDB instance) via injected secrets and doesn't need to go through public internet for this kind of communication (instead it uses VPC). My recent problems have begun after I've managed to roll out an software update, that enforced me to make some manual database changes with use of MySQL Workbench and I could not perform this because of local connectivity problems.
Therefore my biggest problem right now is the connectivity to the database from the local machine - I simply can't connect to the RDS instance via MySQL Workbench or even from within the IDE (but it used to work before without such problems). MySQL Workbench gave me following error message as a hint:
After check of given hints from MySQL Workbench I've also checked that:
I use valid database credentials, URL and port (the app in Fargate has the same secrets injected)
Public accessibility flag on RDS is (temporarily) set to "yes"
database security group allows MySQL/Aurora connections from my IP Address range (I've also tested the 0.0.0.0/0 range without further luck)
Therefore my question is: what else should I check to find out the reason of my connectivity failure?
After I've changed my laptop network by switching to the mobile internet the connectivity problem was solved - therefore I suspect, that my laptop was not able to establish the socket connection from the previous network (possibly the communication port or DNS was blocked).
Therefore also don't forget to check the network connectivity by establishing a socket connection like it is described in this answer.
I'm trying to move about 100GB of data from one of my internal hosts up to our new AWS EFS volume.
My first inclination was to use rsync to get a trusted copy up to the volume, but I'm looking at somewhere around 8Mb/s and my first copy operation has taken somewhere around 24 full hours.
I read up on EFS File sync, a utility that's supposed to accelerate the copying operations of large datasets.
In the setup, the instructions dictate that I need to use a ESXi Virtual Image to launch a VM appliance that will connect up to AWS. I believe the recommendation is to use a hypervisor that can be assigned a reachable IP, but I only have my workstation to use.
I'm running into trouble configuring the appliance's network, so that it can handshake with the EFS Agent. I tried using a bridged adapter, but my corporate network uses AD and won't assign an IP to the VM.
Any suggestions?
Hi my goal is to create Active Directory in AWS. I used simple AD and used 2 public and 2 private subnets within the same VPC with the private ones being for the domain controllers. I created an EC2 instance within the same VPC with Windows Server so that I can manage the AD. My EC2 instance joins the domain with no problem. My problem however is I cannot get my local machines on my network to join the AD, as the DC's, are of course private IP's and I cant change the DNS on my machine to these IP's unless on the same network.
Im guessing I need a VPN to join my local network to the Network in the AWS cloud.
Is there a way to achieve having AD in AWS without a VPN such as using an elastic IP with NAT to communicate to the DC's? Or maybe even promoting my EC2 instance to a DC then connecting the local machines DNS to the EC2 instances elastic IP?
Any help is much appreciated and let me know if I am missing any information or not explaining the goal clear enough.
Your question mentions Simple AD. My comments will be for Active Directory in AWS.
Setting up Active Directory in AWS and on-premises is not as easy as I would like it to be. This topic can fill a small book or as Amazon does it, multiple hour long videos. Watch a few while thinking up your solution.
1) Simple AD is not real Active Directory. It is Samba 4, which is very good, but is an Active Directory clone.
2) Do not, and I repeat do not, think about putting Active Directory on a public IP address to serve your on-premises users. The number of ports that you need to open and the risk is just not worth it.
3) Most, if not all, real solutions for configuring Active Directory on-premises and in AWS involve VPNs. Either Direct Connect (DX), hardware routers (Cisco) or site to site VPNs built from OpenSwan or Windows Server.
Note: OpenSwan is very easy to setup, so this is the route I would recommend if cost is a factor. Otherwise look at Cisco ASA type routers (lots of vendors here) for your office and setup a VPN with IPSEC. If cost is not a factor, absolutely go with Direct Connect (DX).
Note: I also use OpenVPN to connect to AD in AWS from home. This setup routes my workstation to a VPC in AWS and is so easy to setup and use. You could start with this to get comfortable with networking to a VPC. There are preconfigured OpenVPN setups in AWS marketplace that are free (user limited).