I’ve got a major learning process I need to go through, but could use a jump start to make sure I get off on the right path…
I have 3 machines I’d like to have communicate with each other over on a private network. • 1 database server (Windows server OS) o Does need RDP access from the office o I do not want to expose the database to the Internet • 2 Windows servers o 1 Web server o 1 Additional server o Both need to be exposed over the Internet (Public network) o Both machines need access to the database server o Both machines have processes that communicate with each other
Planning on using security groups to accept RDP access from the office for all 3 machines.
Is it possible to set up all 3 machines in the same subnet using the default VPC or do I need to create one?
** Edited subject **
March 20, 2018, 06:39 AM
BurtonRW
I thought we were talking about automatic weapons systems...
-Rob
I predict that there will be many suggestions and statements about the law made here, and some of them will be spectacularly wrong. - jhe888
A=A
March 20, 2018, 06:50 AM
ShouldBFishin
quote:
Originally posted by BurtonRW: I thought we were talking about automatic weapons systems...
I think that would be more "fun" than this
March 20, 2018, 08:41 AM
italia
We use AWS S3, but strictly for back-up. All our applications are cloud-based / SaaS services, so AWS just backs up documents, etc.
------------------------------------------------------ Though we choose between reality and madness It's either sadness or euphoria
March 20, 2018, 10:03 AM
zoom6zoom
I can't answer your specific question, but I recently had a gig where I had to set up some AWS stuff for a client. What I can tell you is that their tech support is pretty damn good. Phone calls got connected right away and they knew their stuff.